Triple
T33926570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E869766
|
entity |
| Predicate | workingGroupContext |
P44998
|
FINISHED |
| Object | IETF Security Area |
—
|
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: IETF Security Area | Statement: [RFC 6668, workingGroupContext, IETF Security Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingGroupContext Context triple: [RFC 6668, workingGroupContext, IETF Security Area]
-
A.
workingGroup
Indicates that multiple entities collaborate as a designated team or committee to work together toward a shared task, project, or objective.
-
B.
relatedWorkingGroup
Indicates that there is an associated or connected working group that is relevant to or involved with the referenced entity or activity.
-
C.
workingGroupAcronym
Indicates that an entity is identified by, or associated with, the acronym of a specific working group.
-
D.
organizationContext
chosen
Indicates that one entity operates within, is associated with, or is relevant to the organizational setting or environment defined by another entity.
-
E.
hasWorkingGroupReport
Indicates that an entity is associated with, or has produced, a report generated by a working group.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.