Triple
T618154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian princely states |
E14450
|
entity |
| Predicate | integrationPeriod |
P302
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Indian princely states, integrationPeriod, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationPeriod Context triple: [Indian princely states, integrationPeriod, 1947]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
C.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
D.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
E.
continuedIntoPeriod
Indicates that an action, state, or relationship that began earlier persisted without interruption into a specified later time period.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.