Triple
T35571509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess |
E1027950
|
entity |
| Predicate | hasPopularEndPhase |
P199899
|
FINISHED |
| Object | endgame |
—
|
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: endgame | Statement: [Chess, hasPopularEndPhase, endgame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularEndPhase Context triple: [Chess, hasPopularEndPhase, endgame]
-
A.
hasPopularMiddlePhase
Indicates that an entity has a middle phase or period in its development or lifecycle that is widely recognized as popular or well-regarded.
-
B.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
-
C.
hasMultiplePhases
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
-
D.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
E.
hasChronologicalPhase
Indicates that something is associated with, or occurs during, a specific chronological phase or time period in a sequence of development or events.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69ff632176b0819084610ae2e57ab679 |
completed | May 9, 2026, 4:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.