Triple
T29388505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HFP |
E745313
|
entity |
| Predicate | roleHandsFreeUnitTypicallyImplementedIn |
P166709
|
FINISHED |
| Object | car kits |
—
|
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: car kits | Statement: [HFP, roleHandsFreeUnitTypicallyImplementedIn, car kits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleHandsFreeUnitTypicallyImplementedIn Context triple: [HFP, roleHandsFreeUnitTypicallyImplementedIn, car kits]
-
A.
usesHandGestures
Indicates that an entity communicates or expresses itself by making deliberate movements or signals with its hands.
-
B.
designedForOneHandUse
Indicates that something is intended or optimized to be used comfortably and effectively with only one hand.
-
C.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
E.
wearableBy
Indicates that one entity is designed or suitable to be worn on the body by another entity.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d44b7c8190a79e108c68a7077a |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:40 p.m.