Triple
T29654262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terran |
E750225
|
entity |
| Predicate | constructionMechanic |
P48192
|
FINISHED |
| Object | buildings constructed by SCVs |
—
|
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: buildings constructed by SCVs | Statement: [Terran, constructionMechanic, buildings constructed by SCVs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionMechanic Context triple: [Terran, constructionMechanic, buildings constructed by SCVs]
-
A.
mechanicalExpertise
Indicates that one entity possesses specialized knowledge or skill in understanding, operating, or repairing mechanical systems or devices in relation to another entity or context.
-
B.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
C.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
D.
featuresMechanic
chosen
Indicates that something includes or incorporates a particular mechanic as part of its design or functionality.
-
E.
constructionForm
Indicates the method, style, or structural technique by which something is built or constructed.
- 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 6:54 p.m.