Triple
T34189618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8789 |
E877063
|
entity |
| Predicate | relatesToProcess |
P205359
|
FINISHED |
| Object | Internet Standards Process |
E250273
|
NE 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: Internet Standards Process | Statement: [RFC 8789, relatesToProcess, Internet Standards Process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesToProcess Context triple: [RFC 8789, relatesToProcess, Internet Standards Process]
-
A.
relatedProcessor
Indicates that one processor has a defined relationship or association with another processor, such as being linked, paired, or otherwise connected in processing tasks.
-
B.
relatesToProgram
Indicates that one entity has a relevant connection, association, or involvement with a particular program.
-
C.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
D.
relatesToBranch
Indicates a general association or connection between an entity and a specific branch (such as a subdivision, offshoot, or subunit) within a larger structure or system.
-
E.
relatedToProject
Indicates that an entity has a connection or association with a specific project, without specifying the exact nature of that involvement.
- F. None of above. chosen
Provenance (5 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36cc802938819091ed4e5a896af766 |
completed | June 20, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:55 a.m.