Triple
T1236986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion of Judah |
E26570
|
entity |
| Predicate | explicitlyNamedIn |
P23699
|
FINISHED |
| Object | Revelation 5:5 |
—
|
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 5:5 | Statement: [Lion of Judah, explicitlyNamedIn, Revelation 5:5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explicitlyNamedIn Context triple: [Lion of Judah, explicitlyNamedIn, Revelation 5:5]
-
A.
coNamedWith
Indicates that two or more entities share the same name or are designated by an identical label.
-
B.
isNamedEntity
Indicates that the subject is recognized as a named entity, such as a specific person, organization, location, or other proper noun.
-
C.
areDefinedIn
chosen
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
D.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
E.
isNamedTree
Indicates that the entity is a tree that has been given a specific name or designation.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf3f07c08190a402e8341c1f38cc |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.