Triple
T3621891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annie |
E76744
|
entity |
| Predicate | hasInternationalProductions |
P50493
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Annie, hasInternationalProductions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalProductions Context triple: [Annie, hasInternationalProductions, yes]
-
A.
hasInternationalProductionsIn
Indicates that an entity has produced or staged international versions of its work in the specified location or country.
-
B.
coProductionRegions
Indicates the regions or countries that jointly participated in producing a work (e.g., a film or TV show) as co-producers.
-
C.
hasProductionCompany
Indicates that an entity (such as a film, show, or media work) is associated with a specific company responsible for its production.
-
D.
isProducedIn
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
-
E.
associatedProduction
Indicates that there is a related or connected production (such as a work, performance, or manufacturing process) linked to the subject entity.
- F. None of above. chosen
Provenance (4 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2bb12cc8190bd67597cf3b66a3a |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:23 p.m.