Triple
T29655015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colossus |
E750240
|
entity |
| Predicate | resourceCost |
P115145
|
FINISHED |
| Object | minerals and vespene gas |
—
|
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: minerals and vespene gas | Statement: [Colossus, resourceCost, minerals and vespene gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceCost Context triple: [Colossus, resourceCost, minerals and vespene gas]
-
A.
economicCost
chosen
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
B.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
C.
programCost
Indicates the monetary or resource expenditure required to implement, run, or participate in a particular program.
-
D.
humanCost
Indicates the extent of harm, suffering, or loss experienced by people as a consequence of an action, event, or decision.
-
E.
constructionCost
Indicates the monetary or resource expenditure required to build or construct something.
- 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_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:54 p.m.