Triple
T34523056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cartografía geológica oficial de Chile |
E886327
|
entity |
| Predicate | tipoDeDato |
P18364
|
FINISHED |
| Object | unidades litoestratigráficas |
—
|
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: unidades litoestratigráficas | Statement: [cartografía geológica oficial de Chile, tipoDeDato, unidades litoestratigráficas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeDato Context triple: [cartografía geológica oficial de Chile, tipoDeDato, unidades litoestratigráficas]
-
A.
datumType
chosen
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
B.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
C.
dataDatatype
Indicates that a piece of data is associated with, or constrained to, a specific datatype.
-
D.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
E.
typeOfValue
Indicates that one entity specifies the kind or category of value associated with another entity.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2:02 a.m.