Triple
T28421375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian Developers |
E719948
|
entity |
| Predicate | useTool |
P91992
|
FINISHED |
| Object | Debian bug tracking system |
—
|
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: Debian bug tracking system | Statement: [Debian Developers, useTool, Debian bug tracking system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useTool Context triple: [Debian Developers, useTool, Debian bug tracking system]
-
A.
usesToolFor
chosen
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
B.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
C.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
D.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
E.
officialToolFor
Indicates that one entity is formally designated or authorized as the standard or primary tool to be used for another entity or purpose.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:34 a.m.