Triple
T24428703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Valley-Type lead-zinc district |
E615931
|
entity |
| Predicate | typicalOreTexture |
P31484
|
FINISHED |
| Object | open-space filling |
—
|
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: open-space filling | Statement: [Mississippi Valley-Type lead-zinc district, typicalOreTexture, open-space filling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOreTexture Context triple: [Mississippi Valley-Type lead-zinc district, typicalOreTexture, open-space filling]
-
A.
typicalTexture
chosen
Indicates the usual or characteristic surface feel or consistency that is commonly associated with an entity.
-
B.
primaryOreTypes
Indicates the main types of ore that are predominantly associated with or extracted from a given entity.
-
C.
primaryOreBody
Indicates that an ore body is the main or most significant source of mineralization within a given deposit or mining project.
-
D.
receivesIronOreFrom
Indicates that one entity obtains or is supplied with iron ore from another entity.
-
E.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a983d88190904b559694363a19 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.