Triple
T9408747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glorieta de la Palma |
E226652
|
entity |
| Predicate | hasFormerCentralElement |
P29363
|
FINISHED |
| Object | large palm tree |
—
|
LITERAL 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: large palm tree | Statement: [Glorieta de la Palma, hasFormerCentralElement, large palm tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerCentralElement Context triple: [Glorieta de la Palma, hasFormerCentralElement, large palm tree]
-
A.
hasFormerAnchor
Indicates that an entity previously served as an anchor (e.g., host or main presenter) for another entity, but no longer holds that role.
-
B.
hasFormerUse
chosen
Indicates that something previously served a particular function or role that it no longer has.
-
C.
hasFormerBranchConnection
Indicates a relationship where two entities were previously connected through a branch affiliation that no longer exists.
-
D.
hasFormerService
Indicates that an entity previously provided a service to another entity but no longer does so.
-
E.
hasEarlyCenter
Indicates that an entity possesses or is associated with a primary focal point, hub, or center that occurs or is established earlier than others in time or sequence.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd52547f0c81908ed4f53b9f05ebaa |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.