Triple

T23597635
Position Surface form Disambiguated ID Type / Status
Subject Cava Baja E582661 entity
Predicate partOf P40 FINISHED
Object Madrid historic center
Madrid historic center is the city’s oldest core, known for its narrow medieval streets, historic plazas, and dense concentration of cultural landmarks, bars, and traditional architecture.
E1628961 NE 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: Madrid historic center | Statement: [Cava Baja, partOf, Madrid historic center]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Madrid historic center
Triple: [Cava Baja, partOf, Madrid historic center]
Generated description
Madrid historic center is the city’s oldest core, known for its narrow medieval streets, historic plazas, and dense concentration of cultural landmarks, bars, and traditional architecture.

Provenance (5 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_69e248f9e0a08190814772847003b1ff completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b090a11c8190a33aac35d257e574 completed April 29, 2026, 7:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fc98bd2f48190a0f4d6d0581365c8 completed May 22, 2026, 3:12 a.m.
NEDg Description generation batch_6a0fcd7ae2248190b4583712c9da0afe completed May 22, 2026, 3:28 a.m.
NED2 Entity disambiguation (via description) batch_6a0fce1270608190810926098b7ffbee completed May 22, 2026, 3:31 a.m.
Created at: April 17, 2026, 6:43 p.m.