Triple
T36377810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 578 |
E895952
|
entity |
| Predicate | definesAPI |
P126488
|
FINISHED |
| Object | sys.addaudithook |
—
|
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: sys.addaudithook | Statement: [PEP 578, definesAPI, sys.addaudithook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAPI Context triple: [PEP 578, definesAPI, sys.addaudithook]
-
A.
definesAPIForLanguage
Indicates that one entity specifies or provides the application programming interface (API) to be used by a particular programming language.
-
B.
hasAPIConcept
Indicates that one entity includes, defines, or is associated with a particular API-related concept.
-
C.
definesService
Indicates that one entity specifies or establishes the service provided or implemented by another entity.
-
D.
includesAPI
chosen
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
-
E.
hasAPIs
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:10 p.m.