Triple
T10723874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesus as Lamb of God |
E252888
|
entity |
| Predicate | isAlsoNamedIn |
P35337
|
FINISHED |
| Object | John 1:36 |
—
|
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: John 1:36 | Statement: [Jesus as Lamb of God, isAlsoNamedIn, John 1:36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlsoNamedIn Context triple: [Jesus as Lamb of God, isAlsoNamedIn, John 1:36]
-
A.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
B.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
C.
namedIn
chosen
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
D.
alsoKnownThrough
Indicates that an entity is recognized or identified by means of another entity, such as a source, context, or intermediary, through which its alternative name or identity is known.
-
E.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d46234081908e147638d0cb7e22 |
completed | April 9, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:14 p.m.