Triple
T26164567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Creek dispute |
E654210
|
entity |
| Predicate | hasLegalDimension |
P61304
|
FINISHED |
| Object | international law of the sea |
—
|
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: international law of the sea | Statement: [Sir Creek dispute, hasLegalDimension, international law of the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalDimension Context triple: [Sir Creek dispute, hasLegalDimension, international law of the sea]
-
A.
legalDimension
chosen
Indicates a relationship where something is characterized, evaluated, or framed in terms of its legal aspects, status, or implications.
-
B.
hasLegalCrop
Indicates that an entity is authorized or permitted to cultivate a particular crop in accordance with applicable laws or regulations.
-
C.
hasNationalDimension
Indicates that something possesses a scope, relevance, or impact at the level of a nation or entire country.
-
D.
hasStandardizedDimensions
Indicates that an entity conforms to a predefined, uniform set of measurements or size specifications.
-
E.
hasLegalOrientation
Indicates that an entity possesses a particular legal stance, status, or alignment within a legal framework.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 26, 2026, 8:32 p.m.