Triple
T13935726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chileans |
E335114
|
entity |
| Predicate | identityDocument |
P9070
|
FINISHED |
| Object | Cédula de identidad de 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: Cédula de identidad de Chile | Statement: [Chileans, identityDocument, Cédula de identidad de Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identityDocument Context triple: [Chileans, identityDocument, Cédula de identidad de Chile]
-
A.
typeOfDocumentIssued
Indicates the specific kind or category of document that has been formally issued in a given context.
-
B.
hasIdentityDocument
chosen
Indicates that an entity possesses or is associated with a specific identity document.
-
C.
identificationType
Indicates the specific kind or category of identification associated with an entity or relationship.
-
D.
ianaIdentifierType
Indicates that one entity specifies the type or category of an IANA (Internet Assigned Numbers Authority) identifier associated with another entity.
-
E.
confirmationDocument
Indicates that there exists a document serving as formal confirmation or verification of an action, event, or agreement between entities.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf42878819085146670d7b92605 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.