Triple
T31968518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1119 |
E816244
|
entity |
| Predicate | statusAtTimeOfPublication |
P177599
|
FINISHED |
| Object | Proposed Standard |
—
|
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: Proposed Standard | Statement: [RFC 1119, statusAtTimeOfPublication, Proposed Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAtTimeOfPublication Context triple: [RFC 1119, statusAtTimeOfPublication, Proposed Standard]
-
A.
initialPublicationStatus
Indicates the publication state an item was in at the time it was first released or made publicly available.
-
B.
statusAtTime
Indicates that an entity has a particular status or condition at a specified point in time.
-
C.
publisherStatusAtTime
Indicates the status or condition of a publisher at a specific point in time.
-
D.
documentsStatusAtPublication
chosen
Indicates the status or condition that the documents had at the time they were published.
-
E.
publicationStatus
Indicates the current state or phase of a work within its publication lifecycle, such as draft, under review, published, or retired.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 1, 2026, 12:10 a.m.