Triple
T33048893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagellum Dei |
E845670
|
entity |
| Predicate | grammaticalCaseOfDei |
P140011
|
FINISHED |
| Object | genitive |
—
|
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: genitive | Statement: [Flagellum Dei, grammaticalCaseOfDei, genitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grammaticalCaseOfDei Context triple: [Flagellum Dei, grammaticalCaseOfDei, genitive]
-
A.
grammaticalCaseOf_Dei
chosen
Indicates that one entity specifies the grammatical case associated with the word or expression represented by the other entity.
-
B.
grammaticalCaseOfJesu
Indicates the grammatical case in which the name or form of "Jesu" appears within a given linguistic or textual context.
-
C.
grammaticalCaseOfVirtuti
Indicates the grammatical case assigned to the word or form "virtuti" in a given linguistic context.
-
D.
grammaticalCaseSystem
Indicates a relationship where a language employs a system of grammatical cases to mark the roles and relationships of nouns and related elements in sentences.
-
E.
grammaticalCaseOf_Donum
Indicates that a specified grammatical case is associated with or applied to the word “Donum.”
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.