Triple
T21306160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 23.501 |
E525204
|
entity |
| Predicate | specNumber |
P143668
|
FINISHED |
| Object | 23.501 |
—
|
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: 23.501 | Statement: [3GPP TS 23.501, specNumber, 23.501]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specNumber Context triple: [3GPP TS 23.501, specNumber, 23.501]
-
A.
specType
Indicates the specific type or category of a specification that an entity is associated with.
-
B.
symbolNumber
Indicates a relationship where a specific numerical identifier is assigned to or associated with a particular symbol.
-
C.
hasPartNumber
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
-
D.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
E.
modelNumber
Indicates that one entity is the specific model identifier or code assigned to another entity (such as a product or device).
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa52a508190bb5dc806b6483574 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:05 p.m.