Triple
T37851331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allan Carpenter |
E944062
|
entity |
| Predicate | hasFictionalTimeTravel |
P60994
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Allan Carpenter, hasFictionalTimeTravel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalTimeTravel Context triple: [Allan Carpenter, hasFictionalTimeTravel, yes]
-
A.
hasFictionalTimeAfter
Indicates that one fictional time point or period occurs later than another within a narrative or imagined timeline.
-
B.
fictionalTime
chosen
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
C.
usesTimeTravelFor
Indicates a relationship where an entity employs time travel as a means or method to achieve, affect, or interact with another entity or objective.
-
D.
existsInFictionalTimePeriod
Indicates that an entity is situated within, or associated with, a time period that is fictional rather than part of real-world history.
-
E.
hasTemporalParadox
Indicates that a situation, event, or sequence of events involves a contradiction or inconsistency in time, such as conflicting timelines or causality loops.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
Created at: May 3, 2026, 4:19 p.m.