Triple
T27103902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New South Wales border |
E686511
|
entity |
| Predicate | hasEasternBoundaryWith |
P80556
|
FINISHED |
| Object | Pacific Ocean |
—
|
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: Pacific Ocean | Statement: [New South Wales border, hasEasternBoundaryWith, Pacific Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEasternBoundaryWith Context triple: [New South Wales border, hasEasternBoundaryWith, Pacific Ocean]
-
A.
easternBoundaryFormedBy
chosen
Indicates that the eastern boundary of an area, region, or object is defined or formed by a specified feature or entity.
-
B.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
-
C.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
D.
boundaryTypeEast
Indicates the type or nature of the boundary that lies to the east of a given entity.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with another 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_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 8:49 a.m.