Triple
T5308046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Santiago, Chile |
E120151
|
entity |
| Predicate | politicalRoleSince |
P45811
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [History of Santiago, Chile, politicalRoleSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalRoleSince Context triple: [History of Santiago, Chile, politicalRoleSince, 19th century]
-
A.
currentRepresentativeSince
Indicates the date or time from which an entity has been serving as the current representative of another entity.
-
B.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
C.
governingSince
chosen
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
D.
hasBeenInGovernmentUntil
Indicates that an entity held a government position continuously up to a specified end time or date.
-
E.
namedForPoliticalRole
Indicates that one entity is named after another entity specifically because of that entity’s political office, position, or role.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.