Triple
T34286859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sawyer |
E879761
|
entity |
| Predicate | hasMountingOption |
P34295
|
FINISHED |
| Object | pedestal mounting |
—
|
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: pedestal mounting | Statement: [Sawyer, hasMountingOption, pedestal mounting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMountingOption Context triple: [Sawyer, hasMountingOption, pedestal mounting]
-
A.
hasMountingFeature
chosen
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
B.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
C.
hasBoardingOption
Indicates that an entity offers or is associated with a particular way or method by which passengers or items can board or be taken on.
-
D.
hasMaterialOption
Indicates that an entity can be made from, or is available in, one or more alternative materials.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 1, 2026, 1:57 a.m.