Triple
T37937593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sendelingsdrift ferry crossing |
E946389
|
entity |
| Predicate | oppositeBankLocatedIn |
P195380
|
FINISHED |
| Object | Namibia |
—
|
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: Namibia | Statement: [Sendelingsdrift ferry crossing, oppositeBankLocatedIn, Namibia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeBankLocatedIn Context triple: [Sendelingsdrift ferry crossing, oppositeBankLocatedIn, Namibia]
-
A.
oppositeBankCountry
Indicates that two entities are located on opposing banks of the same river or waterway, each in a different country.
-
B.
isOppositeBankOf
Indicates that one entity is located on the bank of a river or similar water body directly across from the bank where the other entity is located.
-
C.
oppositeBankCity
Indicates that one city is located on the opposite bank of a river from another city.
-
D.
oppositeBankHasPart
Indicates that a bank of a river or similar feature includes, as a component or segment, the bank located on the opposite side.
-
E.
hasOppositeBankStreet
Indicates that a street is located on the opposite bank of a river or waterway relative to another street.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:20 p.m.