Triple
T20696769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&S Space Shot |
E508680
|
entity |
| Predicate | sensation |
P93007
|
FINISHED |
| Object | free-fall sensation |
—
|
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: free-fall sensation | Statement: [S&S Space Shot, sensation, free-fall sensation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensation Context triple: [S&S Space Shot, sensation, free-fall sensation]
-
A.
senses
Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
-
B.
hasSensation
chosen
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
-
C.
sensoryModality
Indicates the type of sensory channel (e.g., visual, auditory, tactile) through which an experience, perception, or information is received or processed.
-
D.
primarySense
Indicates that one sense or meaning of an entity is designated as its main or most central sense among possible alternatives.
-
E.
sensoryCommunication
Indicates a relationship where one entity conveys or exchanges information with another through sensory signals or perception-based means.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1123d7c81908a1d16923437266d |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:10 p.m.