Triple
T27560907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T T.120 |
E695765
|
entity |
| Predicate | applicationProtocolsInclude |
P175190
|
FINISHED |
| Object | T.125 |
—
|
NE NERFINISHED |
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: T.125 | Statement: [ITU-T T.120, applicationProtocolsInclude, T.125]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationProtocolsInclude Context triple: [ITU-T T.120, applicationProtocolsInclude, T.125]
-
A.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
C.
includeProtocol
chosen
Indicates that one entity incorporates or makes use of a specified protocol as part of its operation or definition.
-
D.
applicationLayerProtocol
Indicates that one entity uses, implements, or is associated with a specific application-layer communication protocol in a networked interaction.
-
E.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 27, 2026, 1:39 p.m.