Triple
T10853794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monticello, Iowa |
E256217
|
entity |
| Predicate | hasLocalEventType |
P14526
|
FINISHED |
| Object | community 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: community festivals | Statement: [Monticello, Iowa, hasLocalEventType, community festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalEventType Context triple: [Monticello, Iowa, hasLocalEventType, community festivals]
-
A.
hasEventType
chosen
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
-
C.
hasLocalLevel
Indicates that one entity possesses, is associated with, or is defined at a specific local administrative or organizational level relative to another entity.
-
D.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
E.
hasNearbyEvent
Indicates that an event occurs close in space or time to the referenced entity.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751351a0c8190b38c14888c5e4275 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.