Triple
T19177690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Rodricks |
E469480
|
entity |
| Predicate | timeEffectExperienced |
P127740
|
FINISHED |
| Object | time dilation |
—
|
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: time dilation | Statement: [Jan Rodricks, timeEffectExperienced, time dilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeEffectExperienced Context triple: [Jan Rodricks, timeEffectExperienced, time dilation]
-
A.
temporalEffect
Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
-
B.
timePerception
Indicates how an entity subjectively experiences, interprets, or estimates the passage and duration of time.
-
C.
effectDuration
Indicates the length of time for which an effect remains active or valid.
-
D.
timeDilationLevel
chosen
Indicates the degree to which time is experienced as slowed down or sped up for an entity relative to a reference frame.
-
E.
temporaryEffect
Indicates that one entity causes or experiences an effect that is limited in duration and does not produce a lasting change.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.