Triple
T37456800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spine Crawler |
E930819
|
entity |
| Predicate | requiresResourceVespene |
P188335
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Spine Crawler, requiresResourceVespene, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresResourceVespene Context triple: [Spine Crawler, requiresResourceVespene, false]
-
A.
costsVespene
chosen
Indicates that one entity requires spending a specified amount of vespene resource to obtain, use, or perform the other entity.
-
B.
resourceCostMinerals
Indicates the amount of mineral resources required or consumed to obtain, produce, or use something.
-
C.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
D.
requiresCreep
Indicates that an action, structure, or unit can only be performed, built, or function if it is located on creep.
-
E.
hasNaturalResourceConstraint
Indicates that an entity is subject to limitations or restrictions arising from the availability, quality, or sustainability of natural resources.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 3, 2026, 4:17 p.m.