Triple
T21581168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Range Reconnaissance Imager |
E532526
|
entity |
| Predicate | roleOnSpacecraft |
P140424
|
FINISHED |
| Object | long-range reconnaissance |
—
|
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: long-range reconnaissance | Statement: [Long Range Reconnaissance Imager, roleOnSpacecraft, long-range reconnaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnSpacecraft Context triple: [Long Range Reconnaissance Imager, roleOnSpacecraft, long-range reconnaissance]
-
A.
aboardSpacecraft
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
-
B.
spaceStationRole
Indicates the functional role or duty an entity has in relation to a space station.
-
C.
isOnSpacecraftType
Indicates that one entity is currently aboard or assigned to a spacecraft of a specified type.
-
D.
roleInSpaceShipOneProgram
Indicates that an entity has a specific role or involvement in the SpaceShipOne program.
-
E.
associatedWithSpacecraft
chosen
Indicates a relationship in which an entity is connected or related in some way to a particular spacecraft, such as by operation, design, mission, or support role.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5c496c819093113dd5790fca48 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.