Triple
T1459594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zipaquirá Salt Cathedral area |
E31479
|
entity |
| Predicate | builtWithin |
P14101
|
FINISHED |
| Object | former salt mine |
—
|
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: former salt mine | Statement: [Zipaquirá Salt Cathedral area, builtWithin, former salt mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtWithin Context triple: [Zipaquirá Salt Cathedral area, builtWithin, former salt mine]
-
A.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
B.
placeBuilt
chosen
Indicates that a structure or facility was constructed at a specific location.
-
C.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
buildingIncorporatedInto
Indicates that one building has been structurally or functionally integrated into another building as part of a combined or expanded 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59c1c288190be08064f2d351b2b |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.