Triple
T10623770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC Series Working Group |
E250268
|
entity |
| Predicate | conductsWork |
P1554
|
FINISHED |
| Object | via 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: via IETF mailing lists | Statement: [RFC Series Working Group, conductsWork, via IETF mailing lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductsWork Context triple: [RFC Series Working Group, conductsWork, via IETF mailing lists]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
C.
performsWorkOf
Indicates that one entity carries out, executes, or fulfills the tasks, functions, or role that are normally associated with another entity.
-
D.
conducts
chosen
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
E.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7f11fc8190aed858f2e1443c08 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:52 p.m.