Triple
T18629959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aida (character) |
E455385
|
entity |
| Predicate | finalSceneLocationInStory |
P81796
|
FINISHED |
| Object | tomb beneath the temple |
—
|
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: tomb beneath the temple | Statement: [Aida (character), finalSceneLocationInStory, tomb beneath the temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSceneLocationInStory Context triple: [Aida (character), finalSceneLocationInStory, tomb beneath the temple]
-
A.
climaxLocation
chosen
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
B.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
C.
finalSceneAction
Indicates the action or event that occurs in the concluding or final scene of a narrative or sequence.
-
D.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
E.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f06f4a081909b64f33814577488 |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.