Triple
T29689922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAG (historical) |
E751184
|
entity |
| Predicate | includedProprietaryDrivers |
P36765
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [BLAG (historical), includedProprietaryDrivers, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedProprietaryDrivers Context triple: [BLAG (historical), includedProprietaryDrivers, no]
-
A.
developedDriversFor
Indicates that one entity created or produced software drivers to enable another entity’s hardware or system to function or be controlled.
-
B.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
C.
containsProprietaryComponents
chosen
Indicates that one entity includes or is composed of components that are proprietary (owned, controlled, or restricted by a particular party).
-
D.
driversInField
Indicates that certain drivers are currently present, active, or operating within a specified field or area.
-
E.
hasNotableDriver
Indicates that an entity is associated with a driver who is notable or distinguished in some recognized way.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: April 28, 2026, 7:16 p.m.