Triple
T27052435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barham |
E684808
|
entity |
| Predicate | locatedOppositeState |
P197159
|
FINISHED |
| Object | Victoria |
—
|
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: Victoria | Statement: [Barham, locatedOppositeState, Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOppositeState Context triple: [Barham, locatedOppositeState, Victoria]
-
A.
borderingOpposingState
Indicates that one state shares a border with another state that is politically, militarily, or ideologically opposed to it.
-
B.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
C.
oppositeTownAcrossBorder
Indicates that one town is located directly across a border from another town, positioned as its opposite counterpart.
-
D.
hasNeighboringStateToWest
Indicates that one state is geographically located directly to the west of another state, sharing a common border.
-
E.
cityAtOtherEnd
Indicates that one city is located at the opposite end of a route, connection, or linear feature from another city.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: April 27, 2026, 8:15 a.m.