Triple
T31014799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine contiguous zone |
E790299
|
entity |
| Predicate | innerLimitDistanceFromBaseline |
P7800
|
FINISHED |
| Object | 12 nautical miles |
—
|
LITERAL 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: 12 nautical miles | Statement: [Philippine contiguous zone, innerLimitDistanceFromBaseline, 12 nautical miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innerLimitDistanceFromBaseline Context triple: [Philippine contiguous zone, innerLimitDistanceFromBaseline, 12 nautical miles]
-
A.
innerLimit
Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
-
B.
maximumExtentFromBaseline
chosen
Indicates the greatest distance or deviation of something from a defined baseline reference.
-
C.
hasBaselineLength
Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
-
D.
baselineLimit
Indicates a threshold or maximum baseline level that something is not expected or allowed to exceed.
-
E.
perimeterRuleDistanceLimit
Indicates a constraint that limits how far something may be from a defined perimeter or boundary.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.