Triple
T36878421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odette-Odile in Swan Lake |
E911405
|
entity |
| Predicate | isTitleRoleIn |
P78808
|
FINISHED |
| Object | Swan Lake |
—
|
NE NERFINISHED |
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: Swan Lake | Statement: [Odette-Odile in Swan Lake, isTitleRoleIn, Swan Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTitleRoleIn Context triple: [Odette-Odile in Swan Lake, isTitleRoleIn, Swan Lake]
-
A.
hasTitleRole
chosen
Indicates that an entity holds or is assigned a specific title or role in relation to another entity.
-
B.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
C.
isIndividualTitle
Indicates that a given title refers to a single, specific individual rather than a group, organization, or collective entity.
-
D.
isTitleFor
Indicates that one entity serves as the official title or name designation for another entity.
-
E.
isKeyRole
Indicates that an entity holds a primary or critically important role within a given context or structure.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.