Triple
T29655395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleet Beacon |
E750248
|
entity |
| Predicate | techTreePosition |
P142545
|
FINISHED |
| Object | late Protoss air tech |
—
|
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 Protoss air tech | Statement: [Fleet Beacon, techTreePosition, late Protoss air tech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: techTreePosition Context triple: [Fleet Beacon, techTreePosition, late Protoss air tech]
-
A.
positionOnTreeDiagram
chosen
Indicates the relative location or placement of an element within a hierarchical tree diagram structure.
-
B.
positionOnTreeOfLife
Indicates the relative placement of an entity within the evolutionary hierarchy or branching structure of the tree of life.
-
C.
positionInFamilyTree
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
-
D.
roleInTree
Indicates the specific position or function an entity occupies within a hierarchical tree structure relative to other entities.
-
E.
familyTreeLocation
Indicates the position or role an individual occupies within a family tree relative to other family members.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.