Triple
T27594158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zipkin |
E699849
|
entity |
| Predicate | propagatesContextVia |
P148774
|
FINISHED |
| Object | HTTP headers |
—
|
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 headers | Statement: [Zipkin, propagatesContextVia, HTTP headers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propagatesContextVia Context triple: [Zipkin, propagatesContextVia, HTTP headers]
-
A.
propagateAlong
Indicates that something (such as an effect, signal, or influence) spreads or is transmitted along a specified path, medium, or connection.
-
B.
propagates
Indicates that something causes itself, its effects, or its characteristics to spread or be transmitted from one entity, location, or state to others.
-
C.
propagateAt
Indicates that an effect, signal, or influence spreads or is transmitted to a specific location, time, or context.
-
D.
propulsionContext
Indicates the situational or operational conditions under which a propulsion system functions or is applied.
-
E.
transmitsVia
chosen
Indicates that something is conveyed, sent, or carried from one entity to another through a specified medium, channel, or mechanism.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63056c6a08190857baf73f58aa682 |
completed | May 2, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:06 p.m.