Triple

T30465607
Position Surface form Disambiguated ID Type / Status
Subject Plaza Sotomayor E775128 entity
Predicate locatedNear P294 FINISHED
Object Plaza Aníbal Pinto
Plaza Aníbal Pinto is a central and historic public square in Valparaíso, Chile, known for its surrounding cafés, nightlife, and role as a popular meeting point in the city.
E1951153 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: Plaza Aníbal Pinto | Statement: [Plaza Sotomayor, locatedNear, Plaza Aníbal Pinto]
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: Plaza Aníbal Pinto
Triple: [Plaza Sotomayor, locatedNear, Plaza Aníbal Pinto]
Generated description
Plaza Aníbal Pinto is a central and historic public square in Valparaíso, Chile, known for its surrounding cafés, nightlife, and role as a popular meeting point in the city.

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_69f2249622a48190b1fae2e3e4ee958a completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f686f314fc81908a65eec389e8b1fb completed May 2, 2026, 11:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2958ebd45c8190a80bb7bd1c0f4bcc completed June 10, 2026, 12:30 p.m.
NEDg Description generation batch_6a295cc0d4648190b485c92d4b975781 completed June 10, 2026, 12:46 p.m.
NED2 Entity disambiguation (via description) batch_6a295d3178e88190a032451e8807b8cf completed June 10, 2026, 12:48 p.m.
Created at: April 29, 2026, 8:11 p.m.