Triple
T30217613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dree festival |
E768250
|
entity |
| Predicate | observedInTown |
P8054
|
FINISHED |
| Object | Ziro |
—
|
NE NERFINISHED |
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: Ziro | Statement: [Dree festival, observedInTown, Ziro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedInTown Context triple: [Dree festival, observedInTown, Ziro]
-
A.
usedInTown
Indicates that something is utilized, applied, or functions within the context or boundaries of a particular town.
-
B.
situatedInTown
Indicates that one entity is located within the geographical or administrative boundaries of a specific town.
-
C.
operatesInTown
Indicates that an entity conducts its activities, business, or operations within a particular town.
-
D.
isTown
Indicates that the subject entity is classified as a town.
-
E.
observedInRegion
chosen
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 7:34 p.m.