Triple
T32713609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spacehab-2 |
E836462
|
entity |
| Predicate | locatedInOperation |
P65992
|
FINISHED |
| Object | Space Shuttle payload bay |
E902495
|
NE 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: Space Shuttle payload bay | Statement: [Spacehab-2, locatedInOperation, Space Shuttle payload bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInOperation Context triple: [Spacehab-2, locatedInOperation, Space Shuttle payload bay]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
operationLocation
chosen
Indicates the place or site where an operation, activity, or process is carried out.
-
C.
locationOfOperator
Indicates the place or position where an operator is situated or performs its function.
-
D.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
-
E.
isPartOfOperation
Indicates that one entity functions as a component, phase, or element within a larger, overarching operation.
- F. None of above.
Provenance (4 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a030e31e01881909c6032532cd3c31a |
completed | May 12, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a349eceb9d88190a750b78ab4a04cf7 |
completed | June 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_6a030dadea008190abe0a5652784bdd6 |
completed | May 12, 2026, 11:23 a.m. |
Created at: May 1, 2026, 1:11 a.m.