Triple
T4498267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manawatū River |
E100751
|
entity |
| Predicate | estuaryStatus |
P56908
|
FINISHED |
| Object | Ramsar wetland of international importance |
—
|
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: Ramsar wetland of international importance | Statement: [Manawatū River, estuaryStatus, Ramsar wetland of international importance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estuaryStatus Context triple: [Manawatū River, estuaryStatus, Ramsar wetland of international importance]
-
A.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
B.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
C.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
D.
waterwayStatus
Indicates the current navigational or operational condition of a waterway, such as whether it is open, restricted, or closed for use.
-
E.
formsEstuary
Indicates that a river or watercourse meets a larger body of water in such a way that it creates or constitutes 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56c065e88190934eb0b1632d79bb |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1 p.m.