Triple
T17557030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 517 |
E427614
|
entity |
| Predicate | definesHook |
P127451
|
FINISHED |
| Object | build_wheel |
—
|
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: build_wheel | Statement: [PEP 517, definesHook, build_wheel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesHook Context triple: [PEP 517, definesHook, build_wheel]
-
A.
hookOf
chosen
Indicates that one entity functions as a hook or hooking component that is part of, attached to, or used by another entity.
-
B.
hasHook
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
C.
primaryHook
Indicates that one entity serves as the main or principal connection point, attachment, or linkage for another entity within a given structure or system.
-
D.
definesCommand
Indicates that one entity specifies or establishes a command that another entity can execute or obey.
-
E.
definesRegistry
Indicates that one entity establishes or specifies a registry in which another entity is recorded or managed.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562357b48190bde6f49df0c983c2 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.