Triple
T21522626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rel-18 |
E531011
|
entity |
| Predicate | positionInRoadmap |
P79168
|
FINISHED |
| Object | first major 5G-Advanced release |
—
|
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: first major 5G-Advanced release | Statement: [Rel-18, positionInRoadmap, first major 5G-Advanced release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRoadmap Context triple: [Rel-18, positionInRoadmap, first major 5G-Advanced release]
-
A.
positionInPlan
chosen
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
pilgrimageRoutePosition
Indicates the relative location or stage of an entity along a designated pilgrimage route.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884db3ac81909e77d22d607ac72d |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.