Triple
T35685821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily |
E1031143
|
entity |
| Predicate | hasTrailingWheelCount |
P198932
|
FINISHED |
| Object | 1 pair of trailing 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: 1 pair of trailing wheels | Statement: [Emily, hasTrailingWheelCount, 1 pair of trailing wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailingWheelCount Context triple: [Emily, hasTrailingWheelCount, 1 pair of trailing wheels]
-
A.
hasTrailingWheelArrangement
Indicates that an entity (typically a vehicle) possesses a specific configuration of wheels located at its rear or trailing end.
-
B.
hasNumberOfTrailingAxles
chosen
Indicates the specific count of axles located at the rear (trailing end) of a vehicle or similar object.
-
C.
hasLeadingWheelArrangement
Indicates the specific configuration of the leading (front) wheels in a vehicle’s or locomotive’s wheel arrangement.
-
D.
hasWheelsOption
Indicates that an entity offers or includes a selectable option related to wheels (e.g., presence, type, or configuration of wheels).
-
E.
hasTrailingTruckType
Indicates that an entity is associated with a specific type of truck positioned at the rear or trailing end.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:05 p.m.