Triple
T34686728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torre Glòries |
E890770
|
entity |
| Predicate | hasFormerLocalName |
P76957
|
FINISHED |
| Object | Torre Agbar |
—
|
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: Torre Agbar | Statement: [Torre Glòries, hasFormerLocalName, Torre Agbar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerLocalName Context triple: [Torre Glòries, hasFormerLocalName, Torre Agbar]
-
A.
hasLocalName
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
-
B.
hasLocalNameOrigin
Indicates that the local or commonly used name of an entity originates from, or is derived from, a specified source (such as a language, place, or culture).
-
C.
hasLocalNameFor
Indicates that one entity serves as the local or context-specific name or label used to refer to another entity.
-
D.
mayHaveLocalName
Indicates that an entity can optionally be associated with a locally used or context-specific name.
-
E.
hasNameBeforeChange
chosen
Indicates that an entity is associated with the name it had prior to some change or renaming event.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 1, 2026, 2:05 a.m.