Triple
T16866694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peters |
E410059
|
entity |
| Predicate | modeOfTransportContext |
P28994
|
FINISHED |
| Object | Spaceship |
—
|
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: Spaceship | Statement: [Peters, modeOfTransportContext, Spaceship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfTransportContext Context triple: [Peters, modeOfTransportContext, Spaceship]
-
A.
hasTransportationContext
Indicates that there is a contextual relationship involving transportation modes, conditions, or circumstances relevant to the associated entities or event.
-
B.
transportationContext
chosen
Indicates the situational or environmental conditions under which transportation occurs, such as mode, purpose, or circumstances of travel.
-
C.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
D.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
E.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b5088f208190abfe937633ebe3fe |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.