Triple
T29655320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forge (StarCraft) |
E750247
|
entity |
| Predicate | techTreeRole |
P120019
|
FINISHED |
| Object | core tech structure |
—
|
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: core tech structure | Statement: [Forge (StarCraft), techTreeRole, core tech structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: techTreeRole Context triple: [Forge (StarCraft), techTreeRole, core tech structure]
-
A.
roleInTree
chosen
Indicates the specific position or function an entity occupies within a hierarchical tree structure relative to other entities.
-
B.
taxonomyRole
Indicates that one entity has a specific taxonomic function, status, or role in relation to another entity within a classification or organizational system.
-
C.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
D.
tenantRole
Indicates that an entity holds the role or capacity of a tenant in relation to another entity (such as a property or landlord).
-
E.
technicalRole
Indicates that an entity holds or performs a specific technical function, position, or responsibility in relation to another entity or context.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:54 p.m.