Triple
T30464802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldiers of the cross |
E775104
|
entity |
| Predicate | impliesDutyTo |
P6254
|
FINISHED |
| Object | serve Christ |
—
|
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: serve Christ | Statement: [Soldiers of the cross, impliesDutyTo, serve Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesDutyTo Context triple: [Soldiers of the cross, impliesDutyTo, serve Christ]
-
A.
stressesDutyTo
Indicates that one entity emphasizes or underscores the responsibility, obligation, or duty of another entity.
-
B.
statutoryDuty
Indicates that an entity is legally obligated by statute to perform, refrain from, or ensure a specific action or condition.
-
C.
expectedDuty
Indicates that one entity is obligated or anticipated to perform a particular duty or responsibility toward another entity or within a given context.
-
D.
hasSocialObligationsTo
Indicates that one entity bears social duties, expectations, or responsibilities toward another entity.
-
E.
obligation
chosen
Indicates that one entity is bound or required to perform a duty, action, or fulfill a condition toward another entity or according to a rule or agreement.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:11 p.m.