Triple
T3081823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3168 |
E64274
|
entity |
| Predicate | BCPFor |
P45756
|
FINISHED |
| Object | deployment and use of ECN in IP networks |
—
|
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: deployment and use of ECN in IP networks | Statement: [RFC 3168, BCPFor, deployment and use of ECN in IP networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BCPFor Context triple: [RFC 3168, BCPFor, deployment and use of ECN in IP networks]
-
A.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
B.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
C.
standardizedFor
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
D.
encodingBasisFor
Indicates that one encoding scheme serves as the foundational or reference basis for defining or interpreting another encoding.
-
E.
convertedFor
Indicates that one entity has been transformed, adapted, or reformatted specifically for use, compatibility, or suitability with another entity.
- F. None of above. chosen
Provenance (4 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e70b9081908c801d084a6ae992 |
completed | March 8, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.