Triple
T34523032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cartografía geológica oficial de Chile |
E886327
|
entity |
| Predicate | componente |
P53004
|
FINISHED |
| Object | mapas geológicos impresos |
—
|
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: mapas geológicos impresos | Statement: [cartografía geológica oficial de Chile, componente, mapas geológicos impresos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componente Context triple: [cartografía geológica oficial de Chile, componente, mapas geológicos impresos]
-
A.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
B.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
C.
componentElement
chosen
Indicates that one entity is a constituent or part of another, larger entity or structure.
-
D.
componentFrom
Indicates that one entity is derived from, produced by, or originates as a component of another entity.
-
E.
componentCC
Indicates that one entity is a component or constituent part of another entity within a coordinated or composite construction.
- 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_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 2:02 a.m.