Triple
T29306799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8554 |
E743115
|
entity |
| Predicate | specifiesUsageIn |
P147990
|
FINISHED |
| Object | Internet protocols |
—
|
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 protocols | Statement: [RFC 8554, specifiesUsageIn, Internet protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesUsageIn Context triple: [RFC 8554, specifiesUsageIn, Internet protocols]
-
A.
usedToSpecify
chosen
Indicates that one entity is employed to define, clarify, or determine the characteristics or identity of another entity.
-
B.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
specifiedFor
Indicates that something is designated or intended to be used for a particular entity, purpose, or context.
-
E.
hasUsageNote
Indicates that there is an associated explanatory note describing how or when something should be used.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 1:14 p.m.