Triple
T29683461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dade Murphy |
E751018
|
entity |
| Predicate | usesComputerHandle |
P10387
|
FINISHED |
| Object | Crash Override |
—
|
NE NERFINISHED |
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: Crash Override | Statement: [Dade Murphy, usesComputerHandle, Crash Override]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesComputerHandle Context triple: [Dade Murphy, usesComputerHandle, Crash Override]
-
A.
usesHandle
Indicates that an entity operates, controls, or interacts with another entity by means of a handle or handled interface.
-
B.
usedInComputerFamily
Indicates that something (such as a component, technology, or design) is employed within or forms part of a particular family or line of computers.
-
C.
hasComputerWorkstations
Indicates that an entity is equipped with or provides access to computer workstations.
-
D.
usesMAC
Indicates that one entity employs or operates another entity via its Media Access Control (MAC) address or MAC-based mechanism.
-
E.
usesSoftware
chosen
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 7:11 p.m.