Triple
T2368144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippians 2:10–11 |
E46029
|
entity |
| Predicate | purposeClause |
P79
|
FINISHED |
| Object | to the glory of God the Father |
—
|
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: to the glory of God the Father | Statement: [Philippians 2:10–11, purposeClause, to the glory of God the Father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeClause Context triple: [Philippians 2:10–11, purposeClause, to the glory of God the Father]
-
A.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
lawStatement
Indicates that an entity expresses, codifies, or articulates a legal rule, principle, or requirement.
-
D.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
E.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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.