Triple
T14892959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Vigils |
E359796
|
entity |
| Predicate | languageOfCelebrationIncludes |
P15031
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Office of Vigils, languageOfCelebrationIncludes, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCelebrationIncludes Context triple: [Office of Vigils, languageOfCelebrationIncludes, Latin]
-
A.
languageOfCeremony
Indicates the language in which a ceremony is conducted or officially performed.
-
B.
isCelebratedIn
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
-
C.
isCelebratedWith
Indicates that an event, occasion, or person is marked or honored using a particular method, activity, or accompanying element (e.g., a party, ritual, or object).
-
D.
languageOfEvent
chosen
Indicates the language in which an event is conducted, presented, or communicated.
-
E.
primaryFestivalLanguage
Indicates that a particular language is the main or officially designated language used for communication and activities at a festival.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f9d10c819091732d7a5a42a682 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:10 a.m.