Triple
T1881586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPDY |
E39862
|
entity |
| Predicate | relationToHTTP |
P37
|
FINISHED |
| Object | acts as a framing layer for HTTP semantics |
—
|
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: acts as a framing layer for HTTP semantics | Statement: [SPDY, relationToHTTP, acts as a framing layer for HTTP semantics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToHTTP Context triple: [SPDY, relationToHTTP, acts as a framing layer for HTTP semantics]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
C.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
D.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
E.
relationshipToWorld
Indicates how an entity is connected or related to the broader world or external environment.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.