Triple
T21224242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 23.272 |
E523049
|
entity |
| Predicate | definesProcedure |
P38228
|
FINISHED |
| Object | CS fallback mobile originating call |
—
|
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: CS fallback mobile originating call | Statement: [3GPP TS 23.272, definesProcedure, CS fallback mobile originating call]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProcedure Context triple: [3GPP TS 23.272, definesProcedure, CS fallback mobile originating call]
-
A.
proceduresDefinedBy
Indicates that certain procedures are specified, established, or authored by a particular entity.
-
B.
definesProcessFor
chosen
Indicates that one entity specifies or establishes the process or procedure to be used for another entity.
-
C.
definesCommand
Indicates that one entity specifies or establishes a command that another entity can execute or obey.
-
D.
definesService
Indicates that one entity specifies or establishes the service provided or implemented by another entity.
-
E.
proceduralRequirement
Indicates that one entity specifies or imposes a required procedure or process that must be followed by another entity.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734a9c9f88190817b574f916886e5 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.