Triple
T3428695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autavia |
E72285
|
entity |
| Predicate | strapOption |
P48675
|
FINISHED |
| Object | leather strap |
—
|
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: leather strap | Statement: [Autavia, strapOption, leather strap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strapOption Context triple: [Autavia, strapOption, leather strap]
-
A.
configurationOptionIn
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
-
B.
strapColor
Indicates the color attribute of a strap associated with an entity.
-
C.
scopeOption
Indicates that one entity specifies or constrains the range, extent, or applicability (scope) of another entity as an available option or setting.
-
D.
upgradeOption
Indicates that one entity serves as a possible improved or higher-level alternative to another entity.
-
E.
bindingOption
Indicates a relationship where one entity specifies or constrains how another entity is bound, attached, or associated within a given context or configuration.
- F. None of above. chosen
Provenance (4 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9854ca081909e637adcac46a27c |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb00f4f8c81908f88daf71f6a9c29 |
completed | March 8, 2026, 5:21 p.m. |
Created at: March 8, 2026, 3:15 p.m.