Triple
T29825251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial of Christ’s death |
E757359
|
entity |
| Predicate | followsCommandOf |
P34528
|
FINISHED |
| Object | Jesus Christ |
—
|
NE NERFINISHED |
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: Jesus Christ | Statement: [Memorial of Christ’s death, followsCommandOf, Jesus Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCommandOf Context triple: [Memorial of Christ’s death, followsCommandOf, Jesus Christ]
-
A.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
B.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
C.
successorInCommand
Indicates that one entity is designated to assume command authority immediately after another entity, typically when the latter is unavailable or their term ends.
-
D.
followsLeadershipOf
chosen
Indicates that one entity accepts and acts under the guidance, direction, or authority of another entity’s leadership.
-
E.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 5:31 p.m.