Triple
T32872872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigilia Nativitatis Domini |
E840837
|
entity |
| Predicate | hasLatinTerm |
P198116
|
FINISHED |
| Object | vigilia |
—
|
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: vigilia | Statement: [Vigilia Nativitatis Domini, hasLatinTerm, vigilia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatinTerm Context triple: [Vigilia Nativitatis Domini, hasLatinTerm, vigilia]
-
A.
hasLatinName
Indicates that an entity is associated with a specific Latin (scientific) name.
-
B.
hasLatinNameMeaning
Indicates that an entity’s Latin name conveys a specific meaning or refers to a particular concept.
-
C.
hasLatinEtymology
Indicates that something originates from or is derived from a Latin word or linguistic root.
-
D.
hasLatinPhraseMeaning
Indicates that one entity is a Latin phrase that expresses the meaning or translation of another entity.
-
E.
hasLatinizedName
Indicates that an entity is associated with a version of its name that has been converted into Latin form or spelling.
- F. None of above. chosen
Provenance (4 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
| PDg | Predicate description generation | batch_69fecb4be24481908bda6197d7fc32f4 |
completed | May 9, 2026, 5:51 a.m. |
Created at: May 1, 2026, 1:17 a.m.