Triple
T3093848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3710 |
E64545
|
entity |
| Predicate | updatesProcess |
P6360
|
FINISHED |
| Object | Internet standards process |
—
|
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: Internet standards process | Statement: [RFC 3710, updatesProcess, Internet standards process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesProcess Context triple: [RFC 3710, updatesProcess, Internet standards process]
-
A.
updateProcess
chosen
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
B.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
C.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another entity.
-
D.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
-
E.
updatesSpecificationOf
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada23876a4819095bfc28640d8c200 |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.