Triple
T10928746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1665 |
E258142
|
entity |
| Predicate | updatesStatusOf |
P35872
|
FINISHED |
| Object | early Internet routing standards |
—
|
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: early Internet routing standards | Statement: [RFC 1665, updatesStatusOf, early Internet routing standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesStatusOf Context triple: [RFC 1665, updatesStatusOf, early Internet routing standards]
-
A.
upgradedStatusTo
Indicates that one entity has changed another entity’s status or level to a higher or more advanced state.
-
B.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
-
C.
statusChange
chosen
Indicates a transition in an entity’s state or condition from one status to another over time.
-
D.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another entity.
-
E.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709eb0ec819093f7d3f99097bbe4 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.