Triple
T26164543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Creek dispute |
E654210
|
entity |
| Predicate | hasClaimBy |
P73422
|
FINISHED |
| Object | India |
E1124
|
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: India | Statement: [Sir Creek dispute, hasClaimBy, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClaimBy Context triple: [Sir Creek dispute, hasClaimBy, India]
-
A.
hasClaimOn
chosen
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
B.
hasClaimType
Indicates that an entity is associated with or categorized under a specific type of claim.
-
C.
hasClaimsOperationsIn
Indicates that an entity performs, manages, or is responsible for claims-related operations within a specified location, region, or organizational unit.
-
D.
supportsClaim
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
-
E.
requiresClaim
Indicates that one entity can only be accessed, used, or fulfilled if a specific claim or entitlement has first been asserted or verified.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a118f96b900819091ac0262af96ea86 |
completed | May 23, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 26, 2026, 8:32 p.m.