Triple
T36620458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake No |
E904021
|
entity |
| Predicate | wetlandSystem |
P186085
|
FINISHED |
| Object | Sudd |
—
|
NE NERFINISHED |
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: Sudd | Statement: [Lake No, wetlandSystem, Sudd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wetlandSystem Context triple: [Lake No, wetlandSystem, Sudd]
-
A.
wetlandType
Indicates the specific classification or category of wetland associated with an entity.
-
B.
wetlandStatus
Indicates whether an area or site is classified as a wetland and, if so, what its specific wetland designation or condition is.
-
C.
containsWetland
Indicates that one area or region includes within its boundaries a wetland ecosystem.
-
D.
formsWetland
Indicates that one entity creates, develops, or gives rise to a wetland environment in relation to another entity or location.
-
E.
isUrbanWetland
Indicates that a location or area functions as a wetland situated within or adjacent to an urban or heavily developed environment.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.