Triple
T36290573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steyr-Puch 500 |
E893214
|
entity |
| Predicate | wheelbaseComparableTo |
P143504
|
FINISHED |
| Object | Fiat 500 |
—
|
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: Fiat 500 | Statement: [Steyr-Puch 500, wheelbaseComparableTo, Fiat 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelbaseComparableTo Context triple: [Steyr-Puch 500, wheelbaseComparableTo, Fiat 500]
-
A.
wheelbaseComparedTo
chosen
Indicates a comparison between the distances between the front and rear wheel axles (wheelbases) of two entities, specifying how one wheelbase relates in size or length to the other.
-
B.
wheelbase
Indicates the distance between the centers of the front and rear wheels of a vehicle.
-
C.
wheelbaseClass
Indicates the classification of a vehicle based on the length or category of its wheelbase.
-
D.
wheelbaseVariantOf
Indicates a relationship where one vehicle’s wheelbase configuration is a variant or modified version of another vehicle’s wheelbase.
-
E.
wheelbaseSharedWith
Indicates that two vehicles have the same wheelbase dimensions or share a common wheelbase platform.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.