Triple
T3627160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princely State of Porbandar |
E76865
|
entity |
| Predicate | sovereigntyEnded |
P43452
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Princely State of Porbandar, sovereigntyEnded, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereigntyEnded Context triple: [Princely State of Porbandar, sovereigntyEnded, mid-20th century]
-
A.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
B.
fullSovereigntyTransferred
Indicates that complete and exclusive governing authority has been formally transferred from one entity to another.
-
C.
wasIndependentUntil
chosen
Indicates that an entity possessed independent status or autonomy up to a specific point in time, after which that independence ceased.
-
D.
sovereignStateAfter
Indicates that one sovereign state succeeds another as its political or legal successor in time.
-
E.
wasKingdomUntil
Indicates that an entity functioned as a kingdom governing another entity up to a specified end time or event.
- 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_69adc2ddccc881909ae13dca3dd8a11d |
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.