Triple
T16498474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Coming |
E400742
|
entity |
| Predicate | followsAfterNumberOfYears |
P76474
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Second Coming, followsAfterNumberOfYears, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsAfterNumberOfYears Context triple: [Second Coming, followsAfterNumberOfYears, 5]
-
A.
followsAfterNumberOfDays
Indicates that one event or state occurs after another by a specified number of days.
-
B.
coversYearsTo
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
-
C.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
D.
yearPassed
chosen
Indicates that a specified number of calendar years has elapsed between two time points or events.
-
E.
countsYearsFrom
Indicates a temporal relationship where the number of years is measured starting from a specified reference point or 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e3505f48190a6891a5f29377212 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.