Triple
T32236800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Dirt Region of Orange County |
E823490
|
entity |
| Predicate | originOfSoils |
P48944
|
FINISHED |
| Object | glacial lake sediments |
—
|
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: glacial lake sediments | Statement: [Black Dirt Region of Orange County, originOfSoils, glacial lake sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfSoils Context triple: [Black Dirt Region of Orange County, originOfSoils, glacial lake sediments]
-
A.
soilOrigin
chosen
Indicates the source or provenance from which a given soil was formed or obtained.
-
B.
soilOrder
Indicates the classification relationship that assigns a soil entity to a specific soil order within a soil taxonomy system.
-
C.
soilRepresents
Indicates that one soil sample, type, or condition stands for, symbolizes, or serves as a proxy for another soil-related state or concept.
-
D.
sedimentSource
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
E.
soilDisposition
Indicates how soil is arranged, oriented, or distributed in relation to surrounding features or conditions.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a017d27e184819094638c3cf6876de4 |
completed | May 11, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_6a017c785a44819083111384b55769e9 |
completed | May 11, 2026, 6:51 a.m. |
Created at: May 1, 2026, 12:39 a.m.