Triple
T1263856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago Metropolitan Region |
E12558
|
entity |
| Predicate | hasCapitalFunction |
P24887
|
FINISHED |
| Object | seat of national government of Chile |
—
|
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: seat of national government of Chile | Statement: [Santiago Metropolitan Region, hasCapitalFunction, seat of national government of Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalFunction Context triple: [Santiago Metropolitan Region, hasCapitalFunction, seat of national government of Chile]
-
A.
hasCapitalType
Indicates that a specified location’s capital is of a particular type (e.g., political, administrative, or economic capital).
-
B.
hasUppercase
Indicates that an entity contains at least one uppercase (capital) letter.
-
C.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
-
D.
capitalizedOn
Indicates that one entity took advantage of, exploited, or made beneficial use of an opportunity, situation, or resource provided or created by another entity.
-
E.
precededByCapital
Indicates that the referenced element is immediately preceded by a capital letter.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc8d6908190a5b2cf1051cc6d5e |
completed | March 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc218cb8819090bff71ac7107a03 |
completed | March 1, 2026, 10:22 p.m. |
Created at: March 1, 2026, 7:50 p.m.