Triple
T54033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP |
E1064
|
entity |
| Predicate | introducedFeatureInHTTP1.1 |
P201
|
FINISHED |
| Object | chunked transfer encoding |
—
|
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: chunked transfer encoding | Statement: [HTTP, introducedFeatureInHTTP1.1, chunked transfer encoding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFeatureInHTTP1.1 Context triple: [HTTP, introducedFeatureInHTTP1.1, chunked transfer encoding]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
D.
historicallyImplementedAs
Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
-
E.
introducedConcept
chosen
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.