Triple
T36592834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Clavis David |
E902714
|
entity |
| Predicate | textOpeningLatin |
P90624
|
FINISHED |
| Object | O clavis David et sceptrum domus Israel |
—
|
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: O clavis David et sceptrum domus Israel | Statement: [O Clavis David, textOpeningLatin, O clavis David et sceptrum domus Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textOpeningLatin Context triple: [O Clavis David, textOpeningLatin, O clavis David et sceptrum domus Israel]
-
A.
openingWordsLatin
chosen
Indicates that the opening words of a text, work, or document are expressed in Latin.
-
B.
textOpeningTranslation
Indicates that a text serves as a translation of the opening section of another text.
-
C.
hasLatinIncipit
Indicates that an entity begins with, or is identified by, a specified Latin opening phrase (incipit).
-
D.
hasLatinText
Indicates that an entity possesses or is associated with text written in Latin.
-
E.
mottoTextLatin
Indicates that the relationship specifies the Latin-language wording of an entity's motto.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.