Triple
T19398068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACC |
E485243
|
entity |
| Predicate | canBeDeactivatedBy |
P136300
|
FINISHED |
| Object | driver controls |
—
|
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: driver controls | Statement: [TACC, canBeDeactivatedBy, driver controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDeactivatedBy Context triple: [TACC, canBeDeactivatedBy, driver controls]
-
A.
deactivatedIn
Indicates that an entity has been turned off, disabled, or made inactive within a specified context, system, or time frame.
-
B.
deactivatedAt
Indicates the time or date at which an entity was disabled, turned off, or made inactive.
-
C.
inactivatedBy
Indicates that one entity causes another entity to lose its normal activity, function, or effectiveness.
-
D.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
E.
canBeDisabledOn
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62574edd08190b5456108d5e3907e |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.