Triple
T29195659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8552 |
E740115
|
entity |
| Predicate | definesContentTypeFor |
P125591
|
FINISHED |
| Object | CMS AuthEnvelopedData |
—
|
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: CMS AuthEnvelopedData | Statement: [RFC 8552, definesContentTypeFor, CMS AuthEnvelopedData]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesContentTypeFor Context triple: [RFC 8552, definesContentTypeFor, CMS AuthEnvelopedData]
-
A.
addsContentType
Indicates that one entity augments or associates another entity with a specific content type.
-
B.
governsContentType
chosen
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
C.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
D.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
E.
scriptContentType
Indicates the type or format of the content contained within a script (e.g., language, media, or data type) in relation to that script.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 28, 2026, 12:04 p.m.