Triple
T31517217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calle G |
E804104
|
entity |
| Predicate | hasPlanningEra |
P79132
|
FINISHED |
| Object | 20th century urban development of Vedado |
—
|
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: 20th century urban development of Vedado | Statement: [Calle G, hasPlanningEra, 20th century urban development of Vedado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningEra Context triple: [Calle G, hasPlanningEra, 20th century urban development of Vedado]
-
A.
proposedEra
Indicates that one entity has suggested or put forward a particular era or time period as relevant or applicable to another entity or context.
-
B.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
C.
hasPlanningOrigin
Indicates that something originates from, or is derived from, a particular planning process, plan, or planning context.
-
D.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
E.
hasPlanningContext
chosen
Indicates that an entity is associated with a specific planning-related situation, scope, or set of conditions that frame how it should be interpreted or used.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 30, 2026, 9:53 p.m.