Triple
T28031057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1771 |
E708267
|
entity |
| Predicate | publishedBySeries |
P42145
|
FINISHED |
| Object | Request for Comments series |
—
|
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: Request for Comments series | Statement: [RFC 1771, publishedBySeries, Request for Comments series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedBySeries Context triple: [RFC 1771, publishedBySeries, Request for Comments series]
-
A.
hasPublicationSeries
chosen
Indicates that an entity is part of, or associated with, a particular publication series.
-
B.
publicationSeriesType
Indicates the specific kind or category of series to which a publication belongs (e.g., journal series, book series, report series).
-
C.
publisherOfSeries
Indicates that an entity serves as the publishing organization responsible for producing or distributing a particular series.
-
D.
printedInSeries
Indicates that a work was published as part of a particular series or serial publication.
-
E.
relatedPublisherSeries
Indicates a relationship where one publisher’s series is associated with or connected to another publisher’s series, without specifying the exact nature of that connection.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 27, 2026, 8:16 p.m.