Triple
T8786742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playing for Time |
E209059
|
entity |
| Predicate | belongsToCentury |
P56280
|
FINISHED |
| Object | 21st century |
—
|
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: 21st century | Statement: [Playing for Time, belongsToCentury, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCentury Context triple: [Playing for Time, belongsToCentury, 21st century]
-
A.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
B.
associatedWithCentury
chosen
Indicates that something has a relevant connection or linkage to a particular century, such as occurring in, belonging to, or being characteristic of that time period.
-
C.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
D.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
E.
formedInCentury
Indicates that an entity (such as an organization, group, or structure) was established or came into existence during a specified century.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f76f27c819087aadf768df5adbf |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.