Triple
T33345664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dance Sequence |
E853788
|
entity |
| Predicate | hasAwardWinningEntry |
P155315
|
FINISHED |
| Object | Postcards from No Man’s Land |
—
|
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: Postcards from No Man’s Land | Statement: [Dance Sequence, hasAwardWinningEntry, Postcards from No Man’s Land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwardWinningEntry Context triple: [Dance Sequence, hasAwardWinningEntry, Postcards from No Man’s Land]
-
A.
hasAwardWinningPart
Indicates that an entity includes or is associated with a component, role, or element that has received an award for excellence.
-
B.
isWinningEntryOf
chosen
Indicates that one entity is the entry that has won or been selected as the winning submission in a particular contest, competition, or selection process associated with another entity.
-
C.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
D.
hasAwardField
Indicates that an entity’s award is associated with or categorized under a particular field or domain.
-
E.
hasMultipleAwardsPossible
Indicates that an entity is eligible to receive or be associated with more than one award.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.