Triple
T2019881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Christmas |
E44079
|
entity |
| Predicate | centralPlaceOfCelebration |
P7822
|
FINISHED |
| Object | Coptic Orthodox churches |
—
|
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: Coptic Orthodox churches | Statement: [Coptic Christmas, centralPlaceOfCelebration, Coptic Orthodox churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPlaceOfCelebration Context triple: [Coptic Christmas, centralPlaceOfCelebration, Coptic Orthodox churches]
-
A.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
B.
isCelebratedIn
chosen
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
-
C.
seCelebraEn
Indicates that an event or occasion takes place or is held at a specific location or venue.
-
D.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
E.
gatheringPlace
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.