Triple
T30084340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interpreter |
E764559
|
entity |
| Predicate | appearsBeforeEvent |
P11124
|
FINISHED |
| Object | Christian’s arrival at the Cross |
—
|
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: Christian’s arrival at the Cross | Statement: [Interpreter, appearsBeforeEvent, Christian’s arrival at the Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsBeforeEvent Context triple: [Interpreter, appearsBeforeEvent, Christian’s arrival at the Cross]
-
A.
appearsBefore
chosen
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
B.
plannedBeforeEvent
Indicates that one event or action was planned or scheduled to occur prior to a specified reference event.
-
C.
eventBefore
Indicates that one event occurs earlier in time than another event.
-
D.
heirBeforeEvent
Indicates that one entity is designated as the heir of another prior to a specified event occurring.
-
E.
hasPrecedingEvents
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 7:03 p.m.