Triple
T34893293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eva de Fábregas |
E1006358
|
entity |
| Predicate | storyEnvironment |
P35676
|
FINISHED |
| Object | ocean voyage |
—
|
LITERAL 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: ocean voyage | Statement: [Eva de Fábregas, storyEnvironment, ocean voyage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyEnvironment Context triple: [Eva de Fábregas, storyEnvironment, ocean voyage]
-
A.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
B.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
storyEngine
Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
-
D.
storySettingEvent
Indicates that an event takes place within, or helps define, the setting or background context of a story.
-
E.
tourEnvironment
Indicates that an entity conducts or participates in a tour within a particular environment or setting.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.