Triple
T1992340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susanna |
E43277
|
entity |
| Predicate | resultOfStory |
P374
|
FINISHED |
| Object | elders are exposed as liars |
—
|
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: elders are exposed as liars | Statement: [Susanna, resultOfStory, elders are exposed as liars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfStory Context triple: [Susanna, resultOfStory, elders are exposed as liars]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
originStorySummary
Indicates a brief narrative explaining how something began, was created, or came into existence.
-
C.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
D.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
E.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.