Triple
T5456145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippolyte et Aricie |
E122482
|
entity |
| Predicate | prologue |
P16777
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hippolyte et Aricie, prologue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prologue Context triple: [Hippolyte et Aricie, prologue, true]
-
A.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
B.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
C.
hasPrologueSometimes
chosen
Indicates that an entity occasionally or in some instances includes a prologue.
-
D.
premise
Indicates that a statement or proposition provides the foundational assumption or starting point from which a conclusion or inference is logically derived.
-
E.
includesSpokenPrologue
Indicates that an entity (such as a work or performance) contains a spoken introductory section delivered before the main content begins.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.