Triple
T3725045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yod |
E81727
|
entity |
| Predicate | usedAsMaterLectionisFor |
P44423
|
FINISHED |
| Object | long i |
—
|
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: long i | Statement: [Yod, usedAsMaterLectionisFor, long i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMaterLectionisFor Context triple: [Yod, usedAsMaterLectionisFor, long i]
-
A.
isMaterLectionis
chosen
Indicates that a letter functions as a mater lectionis, i.e., it represents a vowel sound rather than serving as a consonant.
-
B.
usedInLiturgy
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
C.
liturgicalText
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
D.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
E.
hasLiturgicalReading
Indicates that a religious service, observance, or liturgical event includes or is associated with a specific prescribed reading from scripture or other sacred text.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf54af881908bd8d520595de061 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.