Triple
T159399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado Yule marble |
E3247
|
entity |
| Predicate | purity |
P6859
|
FINISHED |
| Object | high calcite content |
—
|
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: high calcite content | Statement: [Colorado Yule marble, purity, high calcite content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purity Context triple: [Colorado Yule marble, purity, high calcite content]
-
A.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
stance
Indicates the position, attitude, or viewpoint one entity holds toward another entity, issue, or proposition.
-
C.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
D.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
E.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.