Triple
T21460951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riu Plaza |
E529469
|
entity |
| Predicate | locationStrategy |
P8688
|
FINISHED |
| Object | central city locations |
—
|
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: central city locations | Statement: [Riu Plaza, locationStrategy, central city locations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationStrategy Context triple: [Riu Plaza, locationStrategy, central city locations]
-
A.
locationComponent
Indicates that one entity is a constituent or sub-part of a larger location defined by another entity.
-
B.
angularLocation
Indicates the relative position of one entity around another expressed as an angle or direction in a circular or rotational frame.
-
C.
locationPattern
chosen
Indicates a recurring or structured spatial relationship, where an entity consistently appears or is arranged in a particular type of location or spatial configuration.
-
D.
locationFocus
Indicates that the primary or most relevant location associated with an entity, event, or relation is being specified or emphasized.
-
E.
launchLocation
Indicates the place or site from which something is launched or set into motion.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ee10ec8190a606aa64001af35e |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.