Triple
T3627136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princely State of Porbandar |
E76865
|
entity |
| Predicate | wasMaritimeState |
P7803
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Princely State of Porbandar, wasMaritimeState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMaritimeState Context triple: [Princely State of Porbandar, wasMaritimeState, true]
-
A.
coastalState
chosen
Indicates that a state has a coastline adjacent to a sea or ocean, giving it maritime access and jurisdiction over nearby coastal waters.
-
B.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
C.
isSeparatedFromMainlandBy
Indicates that one land area is divided from the mainland by a specific intervening body or feature, such as water or terrain.
-
D.
hasNonCoastalMemberStates
Indicates that within a given group or organization, there exist member states that do not have a coastline.
-
E.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2dc011c8190a6596f4b483fb078 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.