Triple
T24428672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Valley-Type lead-zinc district |
E615931
|
entity |
| Predicate | oreBodyStyle |
P155882
|
FINISHED |
| Object | stratabound |
—
|
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: stratabound | Statement: [Mississippi Valley-Type lead-zinc district, oreBodyStyle, stratabound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oreBodyStyle Context triple: [Mississippi Valley-Type lead-zinc district, oreBodyStyle, stratabound]
-
A.
carBodyStyle
Indicates the specific body configuration or design style that characterizes a car (e.g., sedan, hatchback, SUV).
-
B.
offersBodyStyle
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
C.
appliesToBodyType
Indicates that something (such as a rule, feature, or specification) is relevant or applicable to a particular body type.
-
D.
bodyTypeDepicted
Indicates that one entity visually represents or portrays the physical body type of another entity.
-
E.
hasBodyColor
Indicates that an entity possesses a particular body color as one of its attributes.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:15 a.m.