Triple
T26635904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de la Iglesia |
E668634
|
entity |
| Predicate | oftenRenamedAs |
P170355
|
FINISHED |
| Object | Plaza de Armas |
—
|
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 Armas | Statement: [Plaza de la Iglesia, oftenRenamedAs, Plaza de Armas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRenamedAs Context triple: [Plaza de la Iglesia, oftenRenamedAs, Plaza de Armas]
-
A.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
-
C.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
-
D.
willBeRenamedAs
Indicates that an entity is planned or expected to receive a new name specified by another entity.
-
E.
formedByRenaming
Indicates that one entity is created or derived from another entity specifically through a change of name.
- F. None of above. chosen
Provenance (4 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 2:27 a.m.