Triple
T26119486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuel Becerra |
E658918
|
entity |
| Predicate | squareLocatedAt |
P137525
|
FINISHED |
| Object | Plaza de Manuel Becerra |
—
|
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: Plaza de Manuel Becerra | Statement: [Manuel Becerra, squareLocatedAt, Plaza de Manuel Becerra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: squareLocatedAt Context triple: [Manuel Becerra, squareLocatedAt, Plaza de Manuel Becerra]
-
A.
locationOnSquare
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
-
B.
squareGivenBy
Indicates that one entity is a square (or square-shaped region) that has been specified, defined, or provided by another entity.
-
C.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
D.
squareNamedAfter
chosen
Indicates that a public square is named in honor of, or derived its name from, a particular person, place, event, or entity.
-
E.
squareName
Indicates that an entity is identified by or associated with the name of a square (such as a public square or plaza).
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60aca701c819093f82d6059fa0475 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:07 p.m.