Triple
T931554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infant John the Baptist |
E20102
|
entity |
| Predicate | oftenShownAs |
P4540
|
FINISHED |
| Object | cousin of the Christ Child |
—
|
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: cousin of the Christ Child | Statement: [Infant John the Baptist, oftenShownAs, cousin of the Christ Child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenShownAs Context triple: [Infant John the Baptist, oftenShownAs, cousin of the Christ Child]
-
A.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
B.
announcedAs
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
C.
displayedWith
chosen
Indicates that one entity is shown or presented together alongside another entity in the same context or view.
-
D.
alsoSoldAs
Indicates that one item is marketed or available under an alternative name, label, or product identity.
-
E.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b34b302c81908fa32cb18f551493 |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.