Triple
T22069859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gruvbyn |
E545375
|
entity |
| Predicate | hasResourceExtracted |
P10922
|
FINISHED |
| Object | iron ore |
—
|
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: iron ore | Statement: [Gruvbyn, hasResourceExtracted, iron ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResourceExtracted Context triple: [Gruvbyn, hasResourceExtracted, iron ore]
-
A.
hasExtractionType
Indicates that one entity is associated with a specific method, category, or mode by which something is extracted from it or through it.
-
B.
canExtract
Indicates that one entity has the ability or permission to extract or derive something from another entity or source.
-
C.
canExtractTo
Indicates that one entity is capable of being extracted, converted, or exported into another specified format, location, or representation.
-
D.
resourceExtracted
chosen
Indicates that a resource has been obtained or taken from a source entity, typically through an extraction process.
-
E.
hasResourceBase
Indicates that one entity possesses, is founded on, or derives from another entity serving as its fundamental resource or base.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288724e881908b38fe7e56d3b448 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.