Triple
T34639540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasman Sea region |
E889517
|
entity |
| Predicate | hasMaritimeBoundaryIssuesWith |
P169531
|
FINISHED |
| Object | Australia |
E876
|
NE FINISHED |
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: Australia | Statement: [Tasman Sea region, hasMaritimeBoundaryIssuesWith, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeBoundaryIssuesWith Context triple: [Tasman Sea region, hasMaritimeBoundaryIssuesWith, Australia]
-
A.
hasDisputedMaritimeBoundary
chosen
Indicates that there is an unresolved or contested maritime boundary claim between two or more entities.
-
B.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
C.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
D.
hasTerritorialSeaIn
Indicates that an entity’s territorial sea is located within or extends into the area or jurisdiction of another entity.
-
E.
borderingPoliticalEntityType
Indicates that one political entity is adjacent to and shares a boundary with another political entity of a specified type.
- F. None of above.
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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01bb06422c819095bb42f6f3a0e801 |
completed | May 11, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bd004a081908a03f177d65d5c22 |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a01b9991c348190ac49b65ea2fd86ed |
completed | May 11, 2026, 11:12 a.m. |
Created at: May 1, 2026, 2:04 a.m.