Triple
T24007667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calle de Atocha |
E594433
|
entity |
| Predicate | isInHistoricCoreOf |
P16505
|
FINISHED |
| Object | Madrid |
—
|
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: Madrid | Statement: [Calle de Atocha, isInHistoricCoreOf, Madrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInHistoricCoreOf Context triple: [Calle de Atocha, isInHistoricCoreOf, Madrid]
-
A.
historicalCoreOf
chosen
Indicates that one entity constitutes the original or most historically significant central part of another entity.
-
B.
isInHistoricRegion
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
C.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
D.
isInHistoricRegister
Indicates that an entity has been officially listed or recorded in a recognized historic register or registry.
-
E.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46ba1f88190a204d8cfb0f64be6 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.