Triple
T23363386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 31.101 |
E593243
|
entity |
| Predicate | referenceModelFor |
P115506
|
FINISHED |
| Object | UICC hardware and interface design |
—
|
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: UICC hardware and interface design | Statement: [3GPP TS 31.101, referenceModelFor, UICC hardware and interface design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceModelFor Context triple: [3GPP TS 31.101, referenceModelFor, UICC hardware and interface design]
-
A.
referenceSectionFor
Indicates a relationship where one resource serves as the reference section or reference material specifically associated with another resource.
-
B.
referenceType
Indicates the specific kind or category of reference relationship that one entity has to another.
-
C.
referentRecord
Indicates that one record serves as a reference or pointer to another record within a data or information structure.
-
D.
referenceForm
chosen
Indicates that one entity serves as a reference or canonical form for another entity, typically used as the standard or authoritative version to which others relate.
-
E.
referenceVarietyFor
Indicates that one entity is used as the standard or benchmark variety against which another entity is referenced or compared.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aa0ed88190b0198cbfd1bcc59b |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.