Triple
T4767893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finding in the Temple |
E105855
|
entity |
| Predicate | showsAttributeOfJesus |
P11154
|
FINISHED |
| Object | precocious wisdom |
—
|
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: precocious wisdom | Statement: [Finding in the Temple, showsAttributeOfJesus, precocious wisdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsAttributeOfJesus Context triple: [Finding in the Temple, showsAttributeOfJesus, precocious wisdom]
-
A.
emphasizesAttributeOfChrist
chosen
Indicates that something highlights, underscores, or draws special attention to a particular attribute or quality of Christ.
-
B.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
C.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or entity.
-
D.
hasTouchdownJesusView
Indicates that one entity (typically a location or property) has a view of the landmark known as "Touchdown Jesus."
-
E.
messianicFigureAssociated
Indicates a relationship in which a person, symbol, or concept is linked or connected to a messianic figure, role, or expectation.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.