Triple
T35963177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waubay Lake |
E1040059
|
entity |
| Predicate | isWithinOrAdjacentTo |
P50548
|
FINISHED |
| Object | Waubay National Wildlife Refuge |
—
|
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: Waubay National Wildlife Refuge | Statement: [Waubay Lake, isWithinOrAdjacentTo, Waubay National Wildlife Refuge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinOrAdjacentTo Context triple: [Waubay Lake, isWithinOrAdjacentTo, Waubay National Wildlife Refuge]
-
A.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
B.
locatedInOrAdjacentTo
chosen
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
-
C.
meetsInRelationTo
Indicates that two or more entities come together or interact within the context of a specified relationship or circumstance.
-
D.
hasStructureOnOrAdjacent
Indicates that one entity has a physical structure located on it or immediately next to it.
-
E.
isCloseTo
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
- F. None of above.
Provenance (3 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.