Triple
T33699955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annie |
E863426
|
entity |
| Predicate | chronologicalContextOfWork |
P140037
|
FINISHED |
| Object | 1970s British theatre |
—
|
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: 1970s British theatre | Statement: [Annie, chronologicalContextOfWork, 1970s British theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalContextOfWork Context triple: [Annie, chronologicalContextOfWork, 1970s British theatre]
-
A.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologyPreviousWorkOf
Indicates that one work temporally precedes and is part of the earlier sequence in the overall body of another work.
-
C.
chronologicalSignificance
Indicates that one entity holds importance or relevance specifically due to its position, order, or timing within a chronological sequence relative to another.
-
D.
chronologyIn
chosen
Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
-
E.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:43 a.m.