Triple
T30289000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7482 |
E770319
|
entity |
| Predicate | partOfRDAPSpecificationSet |
P198550
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [RFC 7482, partOfRDAPSpecificationSet, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRDAPSpecificationSet Context triple: [RFC 7482, partOfRDAPSpecificationSet, yes]
-
A.
partlyDesignatedOn
Indicates that something has been assigned or designated only in part or to a limited extent on a particular entity, context, or domain.
-
B.
deJurePartOf
Indicates that one entity is legally or formally recognized as a constituent part or subdivision of another entity, according to official rules or law.
-
C.
consideredPartOf
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
D.
partOfCodeSet
Indicates that something belongs to, or is included within, a specific predefined set of codes.
-
E.
networkPartOf
Indicates that one network is a component or subdivision of a larger, encompassing network.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
| PDg | Predicate description generation | batch_69fef2da7d388190a5712a5094741f18 |
completed | May 9, 2026, 8:39 a.m. |
Created at: April 29, 2026, 7:47 p.m.