Triple
T10156736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transfer-Encoding header field |
E233793
|
entity |
| Predicate | primaryMechanism |
P84491
|
FINISHED |
| Object | chunked transfer coding |
—
|
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 coding | Statement: [Transfer-Encoding header field, primaryMechanism, chunked transfer coding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMechanism Context triple: [Transfer-Encoding header field, primaryMechanism, chunked transfer coding]
-
A.
relatedMechanism
chosen
Indicates a causal or functional connection where one entity serves as the mechanism or process through which another entity’s effect, behavior, or outcome is brought about.
-
B.
primaryDamageType
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
-
C.
killMechanism
Indicates the method or process by which one entity causes the death or destruction of another.
-
D.
formationMechanism
Indicates the process or mechanism by which something is formed, created, or brought into existence.
-
E.
primaryEffect
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec3c47dc81909679903e6024eb49 |
completed | April 2, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.