Triple
T36926811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BVCP |
E913366
|
entity |
| Predicate | rfcTitle |
P164724
|
FINISHED |
| Object | The PPP Bridging Control Protocol (BCP) |
—
|
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: The PPP Bridging Control Protocol (BCP) | Statement: [BVCP, rfcTitle, The PPP Bridging Control Protocol (BCP)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rfcTitle Context triple: [BVCP, rfcTitle, The PPP Bridging Control Protocol (BCP)]
-
A.
hasRFCTitle
chosen
Indicates that an entity is associated with a specific RFC (Request for Comments) document title.
-
B.
CFRTitle
Indicates the specific title within the Code of Federal Regulations under which a referenced regulation or provision is categorized.
-
C.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
D.
canonicalReferenceTitle
Indicates that one entity serves as the standard or authoritative title by which another entity is formally referenced or identified.
-
E.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fde1fbf881909e5474d99404cdfc |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.