Triple
T27103898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New South Wales border |
E686511
|
entity |
| Predicate | hasNorthernBoundaryWith |
P120369
|
FINISHED |
| Object | Queensland |
—
|
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: Queensland | Statement: [New South Wales border, hasNorthernBoundaryWith, Queensland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthernBoundaryWith Context triple: [New South Wales border, hasNorthernBoundaryWith, Queensland]
-
A.
northernBorderLiesAcross
Indicates that the northern border of one region extends across or passes through the area of another region.
-
B.
borderedToNorthBy
Indicates that one entity lies directly to the north of another, sharing a common boundary along its southern edge.
-
C.
geographicallyBorders
Indicates that two geographic entities share a common boundary or border.
-
D.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
E.
borderingPoliticalEntityNorth
chosen
Indicates that one political entity lies directly to the north of, and shares a border with, another political entity.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 27, 2026, 8:49 a.m.