Triple
T1601473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elam Ending |
E34401
|
entity |
| Predicate | phaseOfGameApplied |
P22825
|
FINISHED |
| Object | late-game period |
—
|
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: late-game period | Statement: [Elam Ending, phaseOfGameApplied, late-game period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseOfGameApplied Context triple: [Elam Ending, phaseOfGameApplied, late-game period]
-
A.
majorLeaguePhaseEffect
Indicates that an entity is affected by, or participates in, a specific phase or period within a major league competition or season.
-
B.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
C.
minorLeaguePhaseEffect
Indicates the impact or consequences that a particular phase or stage within a minor league system has on the entities involved.
-
D.
campaignPhase
Indicates the specific stage or period within the lifecycle of a campaign in which an entity or activity currently occurs.
-
E.
upgradePhase
Indicates the stage or step within a process where an entity is being upgraded or transitioned to a more advanced version or state.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.