Triple
T24138512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de San Miguel |
E598156
|
entity |
| Predicate | proximityReasonForFame |
P55574
|
FINISHED |
| Object | proximity to Mercado de San Miguel |
—
|
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: proximity to Mercado de San Miguel | Statement: [Plaza de San Miguel, proximityReasonForFame, proximity to Mercado de San Miguel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityReasonForFame Context triple: [Plaza de San Miguel, proximityReasonForFame, proximity to Mercado de San Miguel]
-
A.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
B.
hasPopularityReason
chosen
Indicates that there is a specific reason or factor explaining why something is popular.
-
C.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
D.
fameStatus
Indicates the level or state of public recognition or renown associated with an entity.
-
E.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7e3c20819099ff289789829d7e |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.