Triple
T30503107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Balloon-Hoax |
E776191
|
entity |
| Predicate | fictionalMeansOfTravel |
P84710
|
FINISHED |
| Object | gas balloon |
—
|
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: gas balloon | Statement: [The Balloon-Hoax, fictionalMeansOfTravel, gas balloon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalMeansOfTravel Context triple: [The Balloon-Hoax, fictionalMeansOfTravel, gas balloon]
-
A.
vehicleOfTimeDisplacement
Indicates a relationship where something serves as the means or mechanism by which time displacement (time travel or temporal shifting) is carried out.
-
B.
fictionalShip
Indicates that one entity is a ship that exists only in fiction or narrative works, rather than in reality.
-
C.
fictionalObject
chosen
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
D.
hasFictionalVehicle
Indicates that one entity possesses, controls, or is associated with a vehicle that exists only in a fictional or imaginary context.
-
E.
fictionalInvention
Indicates that one entity is an invention or creation that exists only within the fictional context of another entity (such as a story, universe, or work).
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 29, 2026, 8:15 p.m.