Triple
T10101610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas Bay |
E216214
|
entity |
| Predicate | hasSediment |
P18668
|
FINISHED |
| Object | sand |
—
|
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 | Statement: [Douglas Bay, hasSediment, sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSediment Context triple: [Douglas Bay, hasSediment, sand]
-
A.
hasSedimentsThat
chosen
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
B.
hasSedimentLoad
Indicates that one entity (typically a water body or flow) carries or transports a certain amount or type of sediment associated with another entity.
-
C.
hasSedimentationIssue
Indicates that an entity experiences or is affected by problems related to the accumulation and settling of particles (sedimentation), often impairing its normal function or quality.
-
D.
typeOfSedimentation
Indicates the specific kind or process of sediment deposition or settling that characterizes how sediment accumulates in a given context.
-
E.
causeOfSediment
Indicates that one entity is the source or generating factor responsible for the formation or presence of sediment in another entity or location.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd099c21c819097aac4f0f168a2da |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.