Triple
T37456799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spine Crawler |
E930819
|
entity |
| Predicate | requiresResourceMinerals |
P90284
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Spine Crawler, requiresResourceMinerals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresResourceMinerals Context triple: [Spine Crawler, requiresResourceMinerals, true]
-
A.
resourceCostMinerals
Indicates the amount of mineral resources required or consumed to obtain, produce, or use something.
-
B.
hasNaturalResourceConstraint
Indicates that an entity is subject to limitations or restrictions arising from the availability, quality, or sustainability of natural resources.
-
C.
miningRequirement
Indicates that one entity specifies a condition or resource that must be obtained through mining for another entity or process to occur or be valid.
-
D.
hasImportantMineral
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
E.
usesNaturalResource
chosen
Indicates that an entity makes use of a natural resource (such as water, minerals, or forests) to support its activities, processes, or functions.
- 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_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 3, 2026, 4:17 p.m.