Triple
T22305363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augmented Backus–Naur Form |
E551359
|
entity |
| Predicate | usedToSpecify |
P147990
|
FINISHED |
| Object | HTTP protocol syntax |
—
|
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: HTTP protocol syntax | Statement: [Augmented Backus–Naur Form, usedToSpecify, HTTP protocol syntax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToSpecify Context triple: [Augmented Backus–Naur Form, usedToSpecify, HTTP protocol syntax]
-
A.
usedToSelect
Indicates that one entity serves as a criterion, tool, or basis for choosing or determining another entity.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
usedToQualify
Indicates that one entity serves as a qualifier or modifier that restricts, specifies, or refines the meaning or scope of another entity.
-
D.
usedToMark
Indicates that one entity serves as a marker, label, or indicator for another entity.
-
E.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
- F. None of above. chosen
Provenance (4 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15726b7e48190b7636db01dbb8a40 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e75dc7b08081909d64441e979c2fa4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 8:41 p.m.