Triple
T10723873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesus as Lamb of God |
E252888
|
entity |
| Predicate | isFirstExplicitlyNamedIn |
P82538
|
FINISHED |
| Object | John 1:29 |
—
|
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:29 | Statement: [Jesus as Lamb of God, isFirstExplicitlyNamedIn, John 1:29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstExplicitlyNamedIn Context triple: [Jesus as Lamb of God, isFirstExplicitlyNamedIn, John 1:29]
-
A.
isExplicit
Indicates that something is stated clearly and directly, leaving no room for ambiguity or implied interpretation.
-
B.
isFirstInCategory
Indicates that an entity is the earliest or primary member within a defined category or group.
-
C.
isEarlyNameOf
Indicates that one name is an earlier or former designation for the same entity as another name.
-
D.
introducedAsNameIn
chosen
Indicates that an entity is presented or referred to by a particular name within a specified context or source.
-
E.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
- 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.