Triple
T10034601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Schwartz |
E204933
|
entity |
| Predicate | transportedToTimePeriod |
P4343
|
FINISHED |
| Object | far future |
—
|
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: far future | Statement: [Joseph Schwartz, transportedToTimePeriod, far future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedToTimePeriod Context triple: [Joseph Schwartz, transportedToTimePeriod, far future]
-
A.
transportedAfter
Indicates that one entity is transported only after the transportation of another entity has occurred in time.
-
B.
transportedOver
Indicates that something is moved or carried across or along a specified medium, route, or surface.
-
C.
wasTransportedTo
Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
-
D.
timeTravelFrom
Indicates a relationship where an entity initiates time travel starting from a specific time or temporal location.
-
E.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4a515c8190baec86d924623b12 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.