Triple
T24041194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Hiz |
E595379
|
entity |
| Predicate | hasSourceGeology |
P46460
|
FINISHED |
| Object | chalk |
—
|
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: chalk | Statement: [River Hiz, hasSourceGeology, chalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceGeology Context triple: [River Hiz, hasSourceGeology, chalk]
-
A.
hasGeologicalNature
Indicates that something possesses a specific geological character, composition, or formation type.
-
B.
hasGeologicResource
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
C.
hasGeologicalUnit
chosen
Indicates that an entity is associated with or contains a specific geological unit, such as a rock layer, formation, or stratigraphic unit.
-
D.
hasGeologicalSignificance
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
-
E.
hasComplexGeology
Indicates that an entity possesses geologic features or structure that are intricate, varied, or highly heterogeneous rather than simple or uniform.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d8b7248190a4e7f152d6bfc2bc |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:57 p.m.