Triple
T30891407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STD 16 |
E786906
|
entity |
| Predicate | hasProtocolScope |
P35569
|
FINISHED |
| Object | Internet core protocols |
—
|
NE NERFINISHED |
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 core protocols | Statement: [STD 16, hasProtocolScope, Internet core protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtocolScope Context triple: [STD 16, hasProtocolScope, Internet core protocols]
-
A.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
C.
hasProtocolRole
Indicates that an entity participates in a protocol by fulfilling a specific role or function within that protocol.
-
D.
protocolScope
chosen
Indicates that one entity defines or constrains the contextual scope within which a particular protocol, procedure, or set of interaction rules applies to another entity.
-
E.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: April 29, 2026, 8:49 p.m.