Triple
T7032543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern |
E163303
|
entity |
| Predicate | hasDrivingWheelDiameter |
P44248
|
FINISHED |
| Object | large driving wheels |
—
|
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: large driving wheels | Statement: [Northern, hasDrivingWheelDiameter, large driving wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingWheelDiameter Context triple: [Northern, hasDrivingWheelDiameter, large driving wheels]
-
A.
wheelDiameter
chosen
Indicates the size of a wheel measured across its diameter.
-
B.
driverDiameter
Indicates the size of the circular cross-section of a driver component, typically measured as the distance across its widest point.
-
C.
formerWheelDiameter
Indicates that one entity was previously the wheel diameter of another entity, but is no longer its current wheel diameter.
-
D.
wheelHeightApprox
Indicates that the height of a wheel is approximately equal to a specified value or to the height of another wheel.
-
E.
numberOfWheels
Indicates the quantity of wheels that an entity possesses or is associated with.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.