Triple
T37496023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger program |
E931828
|
entity |
| Predicate | spacecraftPowerSource |
P191057
|
FINISHED |
| Object | solar panels |
—
|
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: solar panels | Statement: [Ranger program, spacecraftPowerSource, solar panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftPowerSource Context triple: [Ranger program, spacecraftPowerSource, solar panels]
-
A.
spacecraftComponents
Indicates that one entity is a spacecraft and the other is a component or part that belongs to or is used in that spacecraft.
-
B.
spacecraft
Indicates that an entity is a vehicle or object designed to travel or operate in outer space.
-
C.
spacecraftModel
Indicates that one entity is the specific model or design type of a spacecraft associated with another entity.
-
D.
propulsionSource
Indicates the mechanism or system that provides thrust or driving force for an object’s movement.
-
E.
spacecraftBus
Indicates that one entity serves as the primary structural and support platform (bus) for a spacecraft, integrating and housing its subsystems.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 3, 2026, 4:17 p.m.