Triple
T11489518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanam district |
E272366
|
entity |
| Predicate | officialStatusInPuducherry |
P69031
|
FINISHED |
| Object | outlying region of Puducherry |
—
|
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: outlying region of Puducherry | Statement: [Yanam district, officialStatusInPuducherry, outlying region of Puducherry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialStatusInPuducherry Context triple: [Yanam district, officialStatusInPuducherry, outlying region of Puducherry]
-
A.
hasCouncilAreaStatusFrom
Indicates that an entity holds council area status starting from a specified point in time.
-
B.
officialStatusInTerritory
chosen
Indicates that an entity holds a recognized official status, role, or designation within a specified territory or jurisdiction.
-
C.
governingUnionTerritory
Indicates that a specified union territory is the administrative jurisdiction governing or responsible for another entity.
-
D.
hasCouncilAreaStatus
Indicates that an entity holds the official designation or status of being a council area within an administrative or governmental structure.
-
E.
stateInIndia
Indicates that a given state is located within the country of India.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a20df608190992543b4d7006f8a |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.