Triple
T3726084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini 4 |
E81751
|
entity |
| Predicate | spacewalkTool |
P51260
|
FINISHED |
| Object | hand-held maneuvering unit |
—
|
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: hand-held maneuvering unit | Statement: [Gemini 4, spacewalkTool, hand-held maneuvering unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacewalkTool Context triple: [Gemini 4, spacewalkTool, hand-held maneuvering unit]
-
A.
spacewalks
Indicates that an astronaut performs activities outside a spacecraft in open space, typically while wearing a spacesuit and tethered or otherwise supported.
-
B.
spacewalksCount
Indicates the number of spacewalk activities an entity has performed or participated in.
-
C.
spaceCenter
Indicates that one entity serves as a primary facility or hub for space-related operations, missions, or administration for another entity.
-
D.
spaceStationConfiguration
Indicates the specific structural and functional arrangement of modules, systems, and components that define how a space station is organized and operates.
-
E.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
- F. None of above. chosen
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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf669d48190852aaeef70265404 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc226fffc81909c679b44e611fee6 |
completed | March 8, 2026, 6:38 p.m. |
Created at: March 8, 2026, 3:34 p.m.