Triple
T32616043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grey House |
E833786
|
entity |
| Predicate | primaryResidentInFiction |
P205118
|
FINISHED |
| Object | Christian Grey |
E197289
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Christian Grey | Statement: [Grey House, primaryResidentInFiction, Christian Grey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResidentInFiction Context triple: [Grey House, primaryResidentInFiction, Christian Grey]
-
A.
residentInFiction
Indicates that one entity is a fictional character or element that resides or exists within the fictional setting, world, or universe represented by another entity.
-
B.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
C.
stateOfFictionalResidence
Indicates the state or region in which a fictional character’s residence is located.
-
D.
basedInFiction
Indicates that an entity is located or primarily situated within a fictional setting, universe, or narrative world.
-
E.
bornInFictionalSetting
Indicates that a character’s birth occurs within a fictional, imagined, or non-real-world setting.
- F. None of above. chosen
Provenance (5 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34b14d299481908e583b94bb903d1f |
completed | June 19, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:06 a.m.