Triple
T28057230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sons of Jesse |
E708999
|
entity |
| Predicate | symbolicIn |
P89328
|
FINISHED |
| Object | Christian theology |
—
|
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: Christian theology | Statement: [sons of Jesse, symbolicIn, Christian theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicIn Context triple: [sons of Jesse, symbolicIn, Christian theology]
-
A.
symbolizedIn
chosen
Indicates that one entity serves as a symbol or representation of another entity.
-
B.
symbolicRelation
Indicates a relationship where one entity stands for, represents, or conveys meaning about another through symbols or abstract signs.
-
C.
symbolIs
Indicates that one entity serves as the symbolic representation or sign of another entity.
-
D.
hasSymbolicInterpretation
Indicates that one entity is understood or used as a symbolic representation or metaphorical stand-in for another entity or concept.
-
E.
symbolicallyUses
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 8:37 p.m.