Triple
T16768967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epaphroditus |
E407539
|
entity |
| Predicate | honorInstructionIn |
P124567
|
FINISHED |
| Object | Philippians 2:29 |
—
|
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: Philippians 2:29 | Statement: [Epaphroditus, honorInstructionIn, Philippians 2:29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorInstructionIn Context triple: [Epaphroditus, honorInstructionIn, Philippians 2:29]
-
A.
isHonor
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
B.
honorCustom
Indicates that one entity respects, observes, or upholds the traditions, practices, or norms associated with another entity’s custom.
-
C.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
D.
mustRespect
Indicates that one entity is obligated to show respect or deference toward another entity.
-
E.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
- F. None of above. chosen
Provenance (4 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b0349bc88190938750f1e5af192a |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.