Triple
T1008108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Mexican Republic |
E21758
|
entity |
| Predicate | independenceRecognitionDate |
P595
|
FINISHED |
| Object | 1836 |
—
|
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: 1836 | Statement: [First Mexican Republic, independenceRecognitionDate, 1836]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: independenceRecognitionDate Context triple: [First Mexican Republic, independenceRecognitionDate, 1836]
-
A.
independenceRecognized
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
-
B.
independenceDeclaredBy
Indicates that an entity’s independence was formally proclaimed or established by another specified entity.
-
C.
independenceDeclaredFrom
Indicates that one entity has formally declared its independence from another entity, ending or rejecting the latter’s authority or control.
-
D.
independenceYear
chosen
Indicates the year in which an entity achieved political independence or was formally recognized as independent.
-
E.
declaredIndependenceOn
Indicates that an entity formally proclaimed its independence from another authority on a specific date.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.