Triple
T34800869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9FIFTY |
E1003214
|
entity |
| Predicate | fitType |
P86094
|
FINISHED |
| Object | adjustable |
—
|
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: adjustable | Statement: [9FIFTY, fitType, adjustable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fitType Context triple: [9FIFTY, fitType, adjustable]
-
A.
fits
Indicates that one entity is appropriately sized, shaped, or otherwise suitable to be placed in, on, or together with another entity.
-
B.
fittedWith
Indicates that one entity is equipped, supplied, or provided with another entity as a component, feature, or accessory.
-
C.
typicalFit
chosen
Indicates that one entity is a usual, expected, or characteristic match or correspondence for another in a given context.
-
D.
fittedAt
Indicates that something has been installed, adjusted, or made to fit at a specific location or point in time.
-
E.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a89c4e88190a048e95d42b4a084 |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.