Triple
T27471370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide Brooke |
E693327
|
entity |
| Predicate | settingOfKeyStory |
P89733
|
FINISHED |
| Object | Bowie Base One |
—
|
NE NERFINISHED |
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: Bowie Base One | Statement: [Adelaide Brooke, settingOfKeyStory, Bowie Base One]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfKeyStory Context triple: [Adelaide Brooke, settingOfKeyStory, Bowie Base One]
-
A.
settingOfNarration
chosen
Indicates the place, time, or context in which a narrated event or story takes place.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
settingOfNarrator
Indicates that a given location or context serves as the narrative setting in which the narrator’s story or perspective takes place.
-
E.
controlledByInStory
Indicates that, within the context of a specific story or narrative, one entity exercises control or authority over another.
- F. None of above.
Provenance (3 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 12:54 p.m.