Triple
T34779044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Symphony |
E1002589
|
entity |
| Predicate | hasFictionalCellist |
P62476
|
FINISHED |
| Object | Sharon |
—
|
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: Sharon | Statement: [New York Symphony, hasFictionalCellist, Sharon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalCellist Context triple: [New York Symphony, hasFictionalCellist, Sharon]
-
A.
hasFictionalSong
Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
-
B.
isFictionalCharacter
Indicates that the subject is a character that exists only in fiction rather than in real life.
-
C.
isFictionalSong
Indicates that the referenced song exists only in fiction (e.g., within a story, film, game, or other fictional context) and not as a real-world musical work.
-
D.
hasFictionalPerformer
chosen
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
-
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_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: May 3, 2026, 3:59 p.m.