Triple
T37269480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M72 |
E924473
|
entity |
| Predicate | sidecarPosition |
P171229
|
FINISHED |
| Object | right-hand side |
—
|
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: right-hand side | Statement: [M72, sidecarPosition, right-hand side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sidecarPosition Context triple: [M72, sidecarPosition, right-hand side]
-
A.
sidePositionOnSingle
chosen
Indicates the relative lateral placement of one entity on a single, linear reference (such as left/right or side ordering along a single axis).
-
B.
ridingPosition
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
-
C.
supportsSidecar
Indicates that one entity is capable of running, integrating with, or otherwise accommodating a sidecar component alongside its primary process or service.
-
D.
side2Leader
Indicates that the referenced entity serves as the leader or primary representative of the second side in a two-sided relationship, interaction, or conflict.
-
E.
sidecarDrive
Indicates that one entity is driving a motorcycle or similar vehicle while another entity is riding in its attached sidecar.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:15 p.m.