Triple
T22737750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coconino Sandstone |
E562319
|
entity |
| Predicate | mapUnitSymbol |
P149539
|
FINISHED |
| Object | Pc (in some geologic maps) |
—
|
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: Pc (in some geologic maps) | Statement: [Coconino Sandstone, mapUnitSymbol, Pc (in some geologic maps)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapUnitSymbol Context triple: [Coconino Sandstone, mapUnitSymbol, Pc (in some geologic maps)]
-
A.
SIUnitSymbol
Indicates the standardized symbol used to represent a quantity in the International System of Units (SI).
-
B.
dimensionSymbol
Indicates a symbolic notation that represents or labels a specific dimension or measurement attribute in a context.
-
C.
designationUnit
Indicates that one entity serves as the unit or standard of measure used to designate, label, or quantify another entity.
-
D.
fractionalUnitSymbol
Indicates the symbolic notation used to represent the fractional unit associated with a given quantity or measurement.
-
E.
quantitySymbol
Indicates that a particular symbol is used to represent a given quantity in a mathematical, scientific, or formal context.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179707fd081909aed9b2f62b9f842 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:22 p.m.