Triple
T14286832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Doctor is imprisoned on the Valiant |
E354196
|
entity |
| Predicate | occursBeforeEvent |
P42309
|
FINISHED |
| Object | The Doctor’s rejuvenation on the Valiant |
—
|
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: The Doctor’s rejuvenation on the Valiant | Statement: [The Doctor is imprisoned on the Valiant, occursBeforeEvent, The Doctor’s rejuvenation on the Valiant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursBeforeEvent Context triple: [The Doctor is imprisoned on the Valiant, occursBeforeEvent, The Doctor’s rejuvenation on the Valiant]
-
A.
hasPrecedingEvents
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
B.
existedBeforeEvent
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
-
C.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
D.
diesBeforeEvent
Indicates that the subject entity dies at a point in time that occurs before the specified event takes place.
-
E.
eventBefore
chosen
Indicates that one event occurs earlier in time than another 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697ef40c8190bea37724b28c2e99 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.