Triple
T5629567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Absolutely Pure |
E147798
|
entity |
| Predicate | hasAlternativeEnglishRendering |
P3437
|
FINISHED |
| Object | The Most Holy |
—
|
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: The Most Holy | Statement: [The Absolutely Pure, hasAlternativeEnglishRendering, The Most Holy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeEnglishRendering Context triple: [The Absolutely Pure, hasAlternativeEnglishRendering, The Most Holy]
-
A.
hasEnglishName
chosen
Indicates that an entity is associated with a name expressed in the English language.
-
B.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
C.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
D.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
E.
languageOfAlternativeTitle
Indicates the language in which an alternative or variant title of an entity is expressed.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0223c722481908bc3684825b3977a |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.