Triple
T2368158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippians 2:10–11 |
E46029
|
entity |
| Predicate | bowedToBy |
P8708
|
FINISHED |
| Object | every knee |
—
|
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: every knee | Statement: [Philippians 2:10–11, bowedToBy, every knee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowedToBy Context triple: [Philippians 2:10–11, bowedToBy, every knee]
-
A.
paysHomageTo
chosen
Indicates that one entity formally shows respect, reverence, or honor toward another, often acknowledging its superiority, influence, or authority.
-
B.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
C.
respectedAs
Indicates that one entity regards another with esteem or honor, recognizing their value, status, or authority.
-
D.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
E.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76bf75c8190b014c3dbfc46bba3 |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.