Triple
T37215206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5046 |
E922717
|
entity |
| Predicate | definesLayering |
P198593
|
FINISHED |
| Object | MPA over TCP |
—
|
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: MPA over TCP | Statement: [RFC 5046, definesLayering, MPA over TCP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesLayering Context triple: [RFC 5046, definesLayering, MPA over TCP]
-
A.
supportsLayerHierarchy
Indicates that one element can contain and organize other elements within a structured, ordered layer system.
-
B.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
C.
isTypicallyLayered
Indicates that something is usually composed of multiple distinct layers arranged one on top of another.
-
D.
layerType
Indicates the specific kind or category of layer that an entity belongs to or is classified as.
-
E.
usesLayer
Indicates that one entity employs or incorporates a specific layer as part of its structure, configuration, or operation.
- F. None of above. chosen
Provenance (4 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69fef3cdea708190af41c1ff23b68f88 |
completed | May 9, 2026, 8:43 a.m. |
Created at: May 3, 2026, 4:15 p.m.