Triple
T20345688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronas Voe |
E495862
|
entity |
| Predicate | hasShelteredWaters |
P139773
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ronas Voe, hasShelteredWaters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShelteredWaters Context triple: [Ronas Voe, hasShelteredWaters, true]
-
A.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
B.
hasProtectedWatershed
Indicates that an entity possesses or is associated with a watershed area that is legally or formally protected for conservation or resource management purposes.
-
C.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
D.
hasWatersOf
Indicates that a geographic or physical entity contains, is traversed by, or is otherwise characterized by specific bodies or types of water.
-
E.
includesWatersOff
Indicates that a geographic or administrative area’s scope explicitly extends to and covers the adjacent offshore waters.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67838744481909069b76b25dd4bb9 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:24 a.m.