Triple
T19390818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Souss River |
E485061
|
entity |
| Predicate | estuaryImportantFor |
P136268
|
FINISHED |
| Object | migratory birds |
—
|
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: migratory birds | Statement: [Souss River, estuaryImportantFor, migratory birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estuaryImportantFor Context triple: [Souss River, estuaryImportantFor, migratory birds]
-
A.
estuaryDesignation
Indicates that a body of water or coastal area has been formally identified or classified as an estuary.
-
B.
estuaryStatus
Indicates the condition or classification of an estuary, such as its current state, health, or regulatory status.
-
C.
estuaryLocatedIn
Indicates that an estuary is geographically situated within or along the boundaries of a specified larger region or area.
-
D.
locatedInEstuarySystem
Indicates that something is situated within or forms part of an estuary system, where riverine and marine environments interact.
-
E.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b44b70c81908e2f0deeabe4360f |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.