Triple
T21153944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMC Eagle |
E521262
|
entity |
| Predicate | wheelDriveSystemSupplier |
P143085
|
FINISHED |
| Object | Ferguson Formula-derived system |
—
|
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: Ferguson Formula-derived system | Statement: [AMC Eagle, wheelDriveSystemSupplier, Ferguson Formula-derived system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelDriveSystemSupplier Context triple: [AMC Eagle, wheelDriveSystemSupplier, Ferguson Formula-derived system]
-
A.
wheelSupplier
Indicates that one entity supplies or provides wheels to another entity.
-
B.
drivetrainFeature
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
C.
chassisSupplier
Indicates that one entity serves as the supplier or provider of the chassis for another entity.
-
D.
drivetrainConfigurationProduced
Indicates that a particular drivetrain configuration has been produced or manufactured.
-
E.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252929748190afd85be40294293f |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:58 p.m.