Triple
T38644980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devourer |
E938691
|
entity |
| Predicate | isLateGameUnit |
P191319
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Devourer, isLateGameUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLateGameUnit Context triple: [Devourer, isLateGameUnit, true]
-
A.
isGroundUnit
Indicates that an entity functions as a unit operating on or restricted to the ground, as opposed to air, sea, or space units.
-
B.
isEliteUnit
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
C.
isAboutMilitaryUnit
Indicates that something (such as a document, statement, or resource) concerns, discusses, or pertains to a specific military unit.
-
D.
hasLaterFortificationPhase
Indicates that one fortification phase occurs chronologically after another, representing a later stage of defensive construction or modification.
-
E.
isFrontlineUnit
Indicates that an entity functions as a primary combat or operational unit positioned at or near the front line of engagement.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.