Triple
T1941602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripura |
E41565
|
entity |
| Predicate | joinedIndianUnion |
P205
|
FINISHED |
| Object | 15 October 1949 |
—
|
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: 15 October 1949 | Statement: [Tripura, joinedIndianUnion, 15 October 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedIndianUnion Context triple: [Tripura, joinedIndianUnion, 15 October 1949]
-
A.
admittedToUnionOn
chosen
Indicates that an entity (typically a state or region) was formally accepted and incorporated into a union or federation on a specific date.
-
B.
joinedFederalRepublic
Indicates that an entity became a member of, or was incorporated into, a federal republic.
-
C.
admittedToUnionFrom
Indicates that an entity (such as a state or region) was admitted into a union or larger political entity from a specified prior jurisdiction or status.
-
D.
admittedToUnionAsStateNumber
Indicates the ordinal position at which an entity (typically a U.S. state) was formally admitted into a political union as a state.
-
E.
joinedState
Indicates that an entity became a member of, or was incorporated into, a particular state or political union.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.