Triple
T34102189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John 8:12 |
E874602
|
entity |
| Predicate | christologicalTitle |
P179369
|
FINISHED |
| Object | light of the world |
—
|
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: light of the world | Statement: [John 8:12, christologicalTitle, light of the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: christologicalTitle Context triple: [John 8:12, christologicalTitle, light of the world]
-
A.
religiousTitle
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation to another entity.
-
B.
papalTitle
Indicates that a given title is officially held by, or associated with, a pope.
-
C.
honorsTitleOfSaint
Indicates that an entity recognizes or bestows the formal religious title of "saint" upon another entity.
-
D.
isEcclesiasticalTitle
Indicates that the entity functions as a formal religious or church office, rank, or honorific title within an ecclesiastical context.
-
E.
ecclesiasticalTitleUsedIn
Indicates that a particular ecclesiastical (church) title is used within or applies to a specified context, such as a role, office, or jurisdiction.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 1:53 a.m.