Triple
T19221558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Florent-sur-Cher |
E480625
|
entity |
| Predicate | hasCivicEvent |
P2955
|
FINISHED |
| Object | local festivals |
—
|
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: local festivals | Statement: [Saint-Florent-sur-Cher, hasCivicEvent, local festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivicEvent Context triple: [Saint-Florent-sur-Cher, hasCivicEvent, local festivals]
-
A.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
B.
hasCivicOrganization
Indicates that an entity is associated with, supported by, or contains a civic organization, such as a community, volunteer, or public-interest group.
-
C.
hasCulturalEvent
chosen
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
D.
hasCivicElements
Indicates that something includes or involves aspects related to civic life, responsibilities, or public affairs.
-
E.
civicActivity
Indicates participation in or performance of activities related to civic engagement, public service, or community involvement.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3fa9348190920f9d41b8beb900 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:24 p.m.