Triple
T27067694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monterrey |
E685220
|
entity |
| Predicate | mountainLandmark |
P20909
|
FINISHED |
| Object | Cerro de la Silla |
—
|
NE NERFINISHED |
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: Cerro de la Silla | Statement: [Monterrey, mountainLandmark, Cerro de la Silla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainLandmark Context triple: [Monterrey, mountainLandmark, Cerro de la Silla]
-
A.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
-
B.
mountainName
Indicates that an entity is identified by a specific mountain’s name.
-
C.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or entity.
-
D.
notablePeak
chosen
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
E.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622ea4d9081909696af9f5078f2e9 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:26 a.m.