Triple
T30288988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7482 |
E770319
|
entity |
| Predicate | definesQueryMethod |
P132030
|
FINISHED |
| Object | HTTP GET |
—
|
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 GET | Statement: [RFC 7482, definesQueryMethod, HTTP GET]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesQueryMethod Context triple: [RFC 7482, definesQueryMethod, HTTP GET]
-
A.
specifiesMethod
chosen
Indicates that one entity defines or designates the particular method or procedure by which another entity operates or is carried out.
-
B.
methodOfRule
Indicates the specific method, procedure, or approach by which a rule is applied, implemented, or enforced.
-
C.
queryModel
Indicates that an entity requests information or computation from another entity by specifying a particular model to be used for processing the query.
-
D.
bindingMethod
Indicates the technique or process by which two or more entities are joined, attached, or held together.
-
E.
delegateMethod
Indicates that one entity assigns or entrusts a task, responsibility, or operation to another entity to perform on its behalf.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 29, 2026, 7:47 p.m.