Triple
T6488965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Circus |
E147984
|
entity |
| Predicate | restoredVersionReleased |
P66426
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [The Circus, restoredVersionReleased, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredVersionReleased Context triple: [The Circus, restoredVersionReleased, 1969]
-
A.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
B.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
C.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
D.
revivalVersionLabel
chosen
Indicates the specific version identifier or label associated with a revival or restored instance of something (e.g., a document, work, or system).
-
E.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a97fff88190b6f993c14df62649 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.