Triple
T7329116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willakenzie soil |
E168952
|
entity |
| Predicate | hasParentMaterial |
P75362
|
FINISHED |
| Object | marine sedimentary deposits |
—
|
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: marine sedimentary deposits | Statement: [Willakenzie soil, hasParentMaterial, marine sedimentary deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentMaterial Context triple: [Willakenzie soil, hasParentMaterial, marine sedimentary deposits]
-
A.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
B.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
C.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
D.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
-
E.
hasParentWork
Indicates that one work is derived from, contained within, or otherwise subordinate to another, more primary work.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a9c0f081909218560d8a4f4995 |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e80ae5688190ac3d6c1bdf9532f0 |
completed | March 27, 2026, 8:26 p.m. |
Created at: March 27, 2026, 3:03 p.m.