Triple
T34345178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3366 |
E881410
|
entity |
| Predicate | updatesSpecificationType |
P91047
|
FINISHED |
| Object | Point-to-Point Protocol |
—
|
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: Point-to-Point Protocol | Statement: [RFC 3366, updatesSpecificationType, Point-to-Point Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesSpecificationType Context triple: [RFC 3366, updatesSpecificationType, Point-to-Point Protocol]
-
A.
updatesSpecificationOf
Indicates that one entity revises, modifies, or replaces the existing specification of another entity.
-
B.
updatesSpecificationFamily
Indicates that one entity revises, modifies, or brings up to date the specification family associated with another entity.
-
C.
updatesType
chosen
Indicates that one entity modifies, revises, or replaces the type or classification of another entity.
-
D.
updatedSpecificationDate
Indicates the date on which a specification was last revised or brought up to date.
-
E.
updatedSpecificationYear
Indicates the year in which the specification for an entity was last revised or updated.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.