Triple
T28421378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian Developers |
E719948
|
entity |
| Predicate | useCommunicationChannel |
P59911
|
FINISHED |
| Object | Debian mailing lists |
—
|
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 mailing lists | Statement: [Debian Developers, useCommunicationChannel, Debian mailing lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useCommunicationChannel Context triple: [Debian Developers, useCommunicationChannel, Debian mailing lists]
-
A.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
B.
usedToCommunicate
chosen
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
C.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
-
D.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
E.
communicatesFrom
Indicates that information, messages, or signals are sent or expressed from one entity to another.
- 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.