Triple
T15235187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greensand |
E364109
|
entity |
| Predicate | hasGrainSize |
P12318
|
FINISHED |
| Object | sand-sized grains |
—
|
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: sand-sized grains | Statement: [Greensand, hasGrainSize, sand-sized grains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrainSize Context triple: [Greensand, hasGrainSize, sand-sized grains]
-
A.
grainSize
chosen
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
B.
hasGrainType
Indicates that an entity is characterized by or associated with a specific type of grain.
-
C.
hasGrainQuality
Indicates that an entity possesses a particular level or type of grain quality, characterizing the quality attributes of its grain.
-
D.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
E.
hasSpecificGravity
Indicates that one entity has a specific gravity value equal to or characteristic of another entity or reference substance.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d91e4881908ea52d11a3d4480a |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.