Triple
T27752980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Speed Photometer |
E701258
|
entity |
| Predicate | wasOnBoardDuring |
P31585
|
FINISHED |
| Object | Hubble Space Telescope launch |
—
|
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: Hubble Space Telescope launch | Statement: [High Speed Photometer, wasOnBoardDuring, Hubble Space Telescope launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOnBoardDuring Context triple: [High Speed Photometer, wasOnBoardDuring, Hubble Space Telescope launch]
-
A.
usedWhenOnBoard
Indicates that something is employed or utilized while a person or object is on board a vehicle, vessel, or similar conveyance.
-
B.
wasIn
chosen
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
accompaniedDuring
Indicates that one entity was present with and accompanied another entity during a specified event or time period.
-
D.
wasPassengerRelativeOn
Indicates that one entity was a relative of a passenger who was on a specified vehicle, trip, or transport event.
-
E.
wasAmong
Indicates that an entity belonged to, was included in, or was part of a particular group, set, or collection.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6375ece288190bec1ca486bbd2f12 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:21 p.m.