Triple
T28718491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Elysium universe) |
E730025
|
entity |
| Predicate | transportationTo |
P117172
|
FINISHED |
| Object | illegal shuttles to Elysium |
—
|
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: illegal shuttles to Elysium | Statement: [Earth (Elysium universe), transportationTo, illegal shuttles to Elysium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationTo Context triple: [Earth (Elysium universe), transportationTo, illegal shuttles to Elysium]
-
A.
transportModeTo
chosen
Indicates the means or mode of transportation used to travel to a specified destination.
-
B.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
C.
transportGoal
Indicates that an entity has the objective or intended outcome of moving or conveying something or someone from one place to another.
-
D.
transportIndependenceGoal
Indicates a goal or intention for an entity to achieve independence from a particular mode, provider, or system of transportation.
-
E.
transportDevelopment
Indicates the development or improvement of transportation systems, infrastructure, or services connecting places or entities.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 5:52 a.m.