Triple
T4912887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of the Immaculate Conception |
E110275
|
entity |
| Predicate | positionOfStatue |
P59400
|
FINISHED |
| Object | atop Cerro San Cristóbal |
—
|
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: atop Cerro San Cristóbal | Statement: [Sanctuary of the Immaculate Conception, positionOfStatue, atop Cerro San Cristóbal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfStatue Context triple: [Sanctuary of the Immaculate Conception, positionOfStatue, atop Cerro San Cristóbal]
-
A.
statueName
Indicates that a statue has a specific name or title associated with it.
-
B.
statueHeight
Indicates the height measurement of a statue in some specified unit.
-
C.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
D.
sculptorOfFrontStatue
Indicates that one entity is the sculptor who created the statue located at the front of another entity (such as a building or site).
-
E.
statueSubjectRequirement
Indicates that a statue must depict or be associated with a specific required subject or type of subject.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9dc41481908c0c398852e6819c |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6cc228088190849f23b7bd4cf549 |
completed | March 20, 2026, 3:50 p.m. |
Created at: March 20, 2026, 1:29 p.m.