Triple
T34422841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advent in the Ambrosian Rite |
E883593
|
entity |
| Predicate | differsInLengthFrom |
P179648
|
FINISHED |
| Object | Advent in the Roman Rite |
—
|
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: Advent in the Roman Rite | Statement: [Advent in the Ambrosian Rite, differsInLengthFrom, Advent in the Roman Rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differsInLengthFrom Context triple: [Advent in the Ambrosian Rite, differsInLengthFrom, Advent in the Roman Rite]
-
A.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
B.
isDifferenceOf
Indicates that one quantity or entity represents the result obtained by subtracting one specified quantity or entity from another.
-
C.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
D.
hasLexicalDifferencesWith
Indicates that two linguistic items differ from each other in their word choice or lexical form.
-
E.
mayDifferFrom
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2 a.m.