Triple
T18617892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiesta del Sol |
E455076
|
entity |
| Predicate | cityWideSignificance |
P132799
|
FINISHED |
| Object | one of the largest Latino festivals in the Midwest |
—
|
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: one of the largest Latino festivals in the Midwest | Statement: [Fiesta del Sol, cityWideSignificance, one of the largest Latino festivals in the Midwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityWideSignificance Context triple: [Fiesta del Sol, cityWideSignificance, one of the largest Latino festivals in the Midwest]
-
A.
cityWide
Indicates that something applies to, affects, or extends across an entire city.
-
B.
significantUrbanArea
Indicates that a location is classified as a major or important urban center within a broader geographic or administrative context.
-
C.
cityLevel
Indicates the administrative or hierarchical rank of a city within a broader regional or national structure.
-
D.
cityOfInfluence
Indicates the city that significantly shapes, impacts, or exerts influence over a given entity.
-
E.
citySigned
Indicates that a city has formally signed or endorsed an agreement, document, or commitment.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d06c1f8819094fbfa56eca07eaa |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:46 a.m.