Triple
T12714618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Laodicea |
E303804
|
entity |
| Predicate | addressedInChapter |
P36548
|
FINISHED |
| Object | Revelation 3 |
—
|
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: Revelation 3 | Statement: [Church of Laodicea, addressedInChapter, Revelation 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressedInChapter Context triple: [Church of Laodicea, addressedInChapter, Revelation 3]
-
A.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
B.
foundInChapter
chosen
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
C.
sectionAddressed
Indicates that a specific section or part of a document, text, or resource is being referred to, targeted, or dealt with by an action or statement.
-
D.
basedOnChapter
Indicates that something (such as a work, section, or element) is derived from, adapted from, or primarily informed by a specific chapter.
-
E.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620a7554819083784897ff690652 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.