Triple
T30139711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denny Regrade |
E766093
|
entity |
| Predicate | soilDisposition |
P168480
|
FINISHED |
| Object | sluiced material used to fill tideflats |
—
|
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: sluiced material used to fill tideflats | Statement: [Denny Regrade, soilDisposition, sluiced material used to fill tideflats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soilDisposition Context triple: [Denny Regrade, soilDisposition, sluiced material used to fill tideflats]
-
A.
soilOrder
Indicates the classification relationship that assigns a soil entity to a specific soil order within a soil taxonomy system.
-
B.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
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.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
E.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e86d38c8190a100b82da345b6ca |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:17 p.m.