Triple
T34149726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuyalnyk Estuary |
E875961
|
entity |
| Predicate | mudType |
P178443
|
FINISHED |
| Object | sulfide silt mud |
—
|
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: sulfide silt mud | Statement: [Kuyalnyk Estuary, mudType, sulfide silt mud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mudType Context triple: [Kuyalnyk Estuary, mudType, sulfide silt mud]
-
A.
usesMud
Indicates that an entity employs or applies mud as a material, tool, or medium in performing an action or fulfilling a function.
-
B.
MCType
Indicates that an entity is classified as a specific type or category within a multiple-choice (MC) framework.
-
C.
moatType
Indicates the specific kind or classification of moat that characterizes the defensive barrier associated with an entity.
-
D.
mantleType
Indicates the type or classification of a mantle associated with an entity, specifying what kind of mantle it has.
-
E.
primaryMoundType
Indicates the main or dominant type of mound associated with or characterizing an entity.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:54 a.m.