Triple
T425577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T G.8275.1 |
E8199
|
entity |
| Predicate | definesProfileType |
P13755
|
FINISHED |
| Object | full timing support profile |
—
|
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: full timing support profile | Statement: [ITU-T G.8275.1, definesProfileType, full timing support profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProfileType Context triple: [ITU-T G.8275.1, definesProfileType, full timing support profile]
-
A.
definesDeviceType
Indicates that one entity specifies or assigns the device type classification of another entity.
-
B.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
C.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
D.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
E.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb93584819082f23eff13e17c4f |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.