Triple
T8697097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7540 |
E206428
|
entity |
| Predicate | maintainsSemanticsOf |
P74447
|
FINISHED |
| Object | HTTP/1.1 |
—
|
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/1.1 | Statement: [RFC 7540, maintainsSemanticsOf, HTTP/1.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsSemanticsOf Context triple: [RFC 7540, maintainsSemanticsOf, HTTP/1.1]
-
A.
hasSemanticsDefinedBy
chosen
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
B.
hasSemantics
Indicates that one entity carries or encodes the meaning, interpretation, or semantic content associated with another entity.
-
C.
maintainsThrough
Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
-
D.
maintainedAs
Indicates that one entity is kept in a particular state, condition, or configuration by another entity through ongoing care, management, or support.
-
E.
parityMaintainedWith
Indicates that a state of equality or balance (such as value, status, or conditions) is preserved between two entities over time.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582b04688190a439135b08e20451 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.