Triple
T5988340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP Technical Specifications |
E133281
|
entity |
| Predicate | hasVersioningScheme |
P54501
|
FINISHED |
| Object | Release 99 and later |
—
|
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: Release 99 and later | Statement: [3GPP Technical Specifications, hasVersioningScheme, Release 99 and later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersioningScheme Context triple: [3GPP Technical Specifications, hasVersioningScheme, Release 99 and later]
-
A.
supportsVersioning
chosen
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
B.
hasVersionManager
Indicates that one entity is responsible for managing, controlling, or overseeing the versions or revisions of another entity.
-
C.
hasVersionType
Indicates that one entity is associated with a specific kind or category of version of another entity.
-
D.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
-
E.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc51d948190bacf4c40a73e91b2 |
completed | March 22, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.