Triple
T9171044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plates of Ether |
E220079
|
entity |
| Predicate | originStoryIncludes |
P86619
|
FINISHED |
| Object | migration from the Old World to the Americas |
—
|
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: migration from the Old World to the Americas | Statement: [Plates of Ether, originStoryIncludes, migration from the Old World to the Americas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originStoryIncludes Context triple: [Plates of Ether, originStoryIncludes, migration from the Old World to the Americas]
-
A.
originStorySummary
Indicates a brief narrative explaining how something began, was created, or came into existence.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
sourceOfStories
Indicates that one entity serves as the origin or provider of stories for another entity.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
- F. None of above. chosen
Provenance (4 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae38ee48190bf783477bc37913d |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:22 p.m.