Triple
T28005807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF participants |
E707270
|
entity |
| Predicate | communicateVia |
P2798
|
FINISHED |
| Object | IETF mailing lists |
—
|
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: IETF mailing lists | Statement: [IETF participants, communicateVia, IETF mailing lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicateVia Context triple: [IETF participants, communicateVia, IETF mailing lists]
-
A.
communicatesFrom
Indicates that information, messages, or signals are sent or expressed from one entity to another.
-
B.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
C.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
D.
communicationFunction
Indicates that one entity serves a communicative role or purpose in relation to another, such as conveying, mediating, or facilitating the exchange of information.
-
E.
communicationService
Indicates a relationship where one entity provides or facilitates a means for another entity to exchange information or messages.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 8 p.m.