Triple
T1045037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central American independence movement |
E22558
|
entity |
| Predicate | hasKeyDate |
P23987
|
FINISHED |
| Object | 1821-09-15 |
—
|
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: 1821-09-15 | Statement: [Central American independence movement, hasKeyDate, 1821-09-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyDate Context triple: [Central American independence movement, hasKeyDate, 1821-09-15]
-
A.
hasKeyDocument
Indicates that an entity possesses or is associated with a primary or essential document relevant to a particular context or process.
-
B.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
C.
hasKeyAspect
Indicates that something possesses a central, defining, or particularly important feature or characteristic.
-
D.
hasKeyImage
Indicates that one entity is designated as the primary or representative image associated with another entity.
-
E.
hasKeyIssue
Indicates that an entity is associated with a primary or central problem, concern, or topic of importance.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.