Triple
T28748095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Electric–FIAT–Materfer cars |
E731433
|
entity |
| Predicate | propulsionSystemSupplier |
P84477
|
FINISHED |
| Object | General Electric |
—
|
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: General Electric | Statement: [General Electric–FIAT–Materfer cars, propulsionSystemSupplier, General Electric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propulsionSystemSupplier Context triple: [General Electric–FIAT–Materfer cars, propulsionSystemSupplier, General Electric]
-
A.
propulsionContractor
chosen
Indicates that one entity serves as the contractor responsible for providing propulsion systems or propulsion-related services to another entity.
-
B.
propulsionTypeOfSystem
Indicates the type of propulsion mechanism that a system uses to generate thrust or movement.
-
C.
propulsionModule
Indicates a relationship where an entity functions as, or is equipped with, a module responsible for providing propulsion.
-
D.
currentPropulsionSystem
Indicates the propulsion system that an entity is presently using or equipped with.
-
E.
solidRocketBoosterSupplier
Indicates that one entity serves as a supplier of solid rocket boosters to another entity.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b9c36481909d9bf07c60c3dcce |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:06 a.m.