Triple
T31947892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4330 |
E815699
|
entity |
| Predicate | definesScope |
P45871
|
FINISHED |
| Object | SNTP Version 4 for IPv4, IPv6 and OSI |
—
|
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: SNTP Version 4 for IPv4, IPv6 and OSI | Statement: [RFC 4330, definesScope, SNTP Version 4 for IPv4, IPv6 and OSI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesScope Context triple: [RFC 4330, definesScope, SNTP Version 4 for IPv4, IPv6 and OSI]
-
A.
definesScopeFor
chosen
Indicates that one entity establishes or delimits the scope, boundaries, or applicability within which another entity operates or is interpreted.
-
B.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
C.
encodingScope
Indicates the range or extent of content or information that is covered, represented, or captured by a particular encoding.
-
D.
scopeOfReference
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 12:07 a.m.