Triple
T15679077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occultation |
E377523
|
entity |
| Predicate | relatesToTime |
P11533
|
FINISHED |
| Object | end of times |
—
|
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: end of times | Statement: [Occultation, relatesToTime, end of times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesToTime Context triple: [Occultation, relatesToTime, end of times]
-
A.
associatedWithTime
chosen
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
B.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
C.
relatedTimeStandard
Indicates that one time-related entity is defined, interpreted, or aligned according to a particular time standard or reference timescale.
-
D.
hasConceptOfTime
Indicates that an entity possesses an understanding or awareness of time as an abstract concept or measurable dimension.
-
E.
timeCorrelation
Indicates that two events or states are related in time such that changes or occurrences in one are systematically associated with changes or occurrences in the other.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2f1640819086efd5a73bb9734a |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.