Triple
T19260434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ops |
E481632
|
entity |
| Predicate | festival |
P3113
|
FINISHED |
| Object | Opiconsivia |
—
|
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: Opiconsivia | Statement: [Ops, festival, Opiconsivia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Opiconsivia Context triple: [Ops, festival, Opiconsivia]
-
A.
Opiconsivia
chosen
Opiconsivia was an ancient Roman festival dedicated to the goddess Ops Consiva, celebrating the storage and abundance of the harvest.
-
B.
Solita
Solita is a small municipality located in the Caquetá Department of southern Colombia, known for its rural character within the Amazonian foothills region.
-
C.
Toma
Toma is a major Mande language spoken primarily in Guinea and neighboring West African countries.
-
D.
Toma
Toma is a traditional semi-hard cow’s milk cheese from Italy’s Piedmont region, known for its mild, buttery flavor and smooth, elastic texture.
-
E.
Toma
Toma is a masculine given name used in various European cultures, often as a form of Thomas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
Created at: April 10, 2026, 1:28 p.m.