Triple
T11334962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States of India |
E268448
|
entity |
| Predicate | hasDefined |
P23699
|
FINISHED |
| Object | territorial jurisdiction |
—
|
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: territorial jurisdiction | Statement: [States of India, hasDefined, territorial jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefined Context triple: [States of India, hasDefined, territorial jurisdiction]
-
A.
hasDefinition
Indicates that one entity provides the meaning, explanation, or definition of another entity.
-
B.
areDefinedIn
chosen
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
C.
canBeDefinedFor
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
-
D.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
-
E.
hasBeenDeclaredFor
Indicates that an entity has been officially announced, designated, or proclaimed for a particular purpose, status, or context.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.