Triple
T27655058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGB |
E696970
|
entity |
| Predicate | providedInitialPropulsionTo |
P393
|
FINISHED |
| Object | International Space Station |
—
|
NE NERFINISHED |
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: International Space Station | Statement: [FGB, providedInitialPropulsionTo, International Space Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedInitialPropulsionTo Context triple: [FGB, providedInitialPropulsionTo, International Space Station]
-
A.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
B.
laterPropulsion
Indicates that one propulsion system, method, or event occurs after another in time.
-
C.
selfPropelled
Indicates that an entity moves or operates by its own internal power or mechanism, without needing an external force to propel it.
-
D.
propulsionSource
Indicates the mechanism or system that provides thrust or driving force for an object’s movement.
-
E.
propulsion
chosen
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 2:33 p.m.