Triple
T20432436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Peru |
E501164
|
entity |
| Predicate | independenceConsolidated |
P140108
|
FINISHED |
| Object | 1824 |
—
|
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: 1824 | Statement: [History of Peru, independenceConsolidated, 1824]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: independenceConsolidated Context triple: [History of Peru, independenceConsolidated, 1824]
-
A.
independenceRestored
Indicates that a previously dependent or controlled entity has regained its autonomy or self-governance.
-
B.
independenceProcess
Indicates a process or sequence of actions through which an entity becomes or is made independent from another controlling or influencing entity.
-
C.
independenceProvedBy
Indicates that the independence of something (such as a statement, axiom, or system) is established or demonstrated by a particular proof, method, or agent.
-
D.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
E.
independenceProclaimedAt
Indicates the specific time or date at which an entity formally declared its independence.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685eaa4c8819083d1d7aee0f998a6 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:31 a.m.