Triple
T5480710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serving Gateway |
E123459
|
entity |
| Predicate | handlesPlane |
P1490
|
FINISHED |
| Object | user plane |
—
|
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: user plane | Statement: [Serving Gateway, handlesPlane, user plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesPlane Context triple: [Serving Gateway, handlesPlane, user plane]
-
A.
ringPlane
Indicates that one entity lies within or corresponds to the geometric plane defined by a ring structure associated with another entity.
-
B.
plane
Indicates that an entity is a flat, two-dimensional surface extending infinitely in all directions within its dimension.
-
C.
handlingProperty
Indicates that one entity specifies how another entity should be handled, processed, or treated under certain conditions.
-
D.
handlesMaterial
Indicates that an entity is responsible for managing, processing, or otherwise dealing with a specified material.
-
E.
handles
chosen
Indicates that one entity is responsible for dealing with, managing, or taking care of another entity or task.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.