Triple
T13651907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INT for Internet |
E326759
|
entity |
| Predicate | standardizationBodyFor |
P1251
|
FINISHED |
| Object | Internet-related protocols within its scope |
—
|
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-related protocols within its scope | Statement: [INT for Internet, standardizationBodyFor, Internet-related protocols within its scope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizationBodyFor Context triple: [INT for Internet, standardizationBodyFor, Internet-related protocols within its scope]
-
A.
hasStandardizationBody
chosen
Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
-
B.
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.
-
C.
standardBody
Indicates that an entity conforms to a recognized or officially accepted body type, form, or physical specification.
-
D.
standardizationStream
Indicates a process or pathway through which something is standardized or brought into conformity with a common standard.
-
E.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc609676c8190b5b1cabe6b315142 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.