Triple
T33149016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanam region |
E848384
|
entity |
| Predicate | administrativelyMergedIntoPuducherryOn |
P194373
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Yanam region, administrativelyMergedIntoPuducherryOn, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativelyMergedIntoPuducherryOn Context triple: [Yanam region, administrativelyMergedIntoPuducherryOn, 1962]
-
A.
establishedAsUnionTerritoryOn
Indicates the date or event on which a region was formally designated and constituted as a union territory.
-
B.
wasUnionTerritoryAs
Indicates that an entity held the status of a union territory during a specified time or under specified conditions.
-
C.
integratedIntoIndianUnionAs
Indicates that an entity (such as a region or princely state) was formally incorporated into the political and administrative framework of the Indian Union.
-
D.
governedIndiaUntil
Indicates that a subject held governing authority over India up to a specified end time or date.
-
E.
wasPrincelyStateUntil
Indicates that an entity held the status of a princely state up to a specified end date or time period.
- F. None of above. chosen
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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 1, 2026, 1:28 a.m.