Triple
T34779034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Symphony |
E1002589
|
entity |
| Predicate | hasFictionalBoardMember |
P141846
|
FINISHED |
| Object | Gloria Windsor |
—
|
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: Gloria Windsor | Statement: [New York Symphony, hasFictionalBoardMember, Gloria Windsor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalBoardMember Context triple: [New York Symphony, hasFictionalBoardMember, Gloria Windsor]
-
A.
hasFictionalMember
chosen
Indicates that a group, organization, or collection includes at least one member that is fictional rather than real.
-
B.
hasFictionalStaffMember
Indicates that an entity includes or employs a staff member who is a fictional character.
-
C.
hasFictionalLeader
Indicates that an entity is led or governed by a leader who is a fictional character rather than a real person.
-
D.
hasFictionalSpokesperson
Indicates that an entity is represented or promoted by a spokesperson who is a fictional or imaginary character.
-
E.
hasFictionalSpeaker
Indicates that a work, text, or expression is presented as being spoken by an invented or non-real speaker rather than an actual person.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 3:59 p.m.