Triple
T332270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee marble |
E6649
|
entity |
| Predicate | trueRockType |
P1326
|
FINISHED |
| Object | limestone |
—
|
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: limestone | Statement: [Tennessee marble, trueRockType, limestone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trueRockType Context triple: [Tennessee marble, trueRockType, limestone]
-
A.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
C.
coneType
Indicates the specific category or style of cone associated with an entity (e.g., type, shape, or design of the cone).
-
D.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
E.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eab1a7048190ac690ddc2e294914 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.