Triple
T17659385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T Study Group 16 |
E440208
|
entity |
| Predicate | standardized |
P1371
|
FINISHED |
| Object |
T.38
T.38 is an ITU-T recommendation that defines a protocol for real-time fax transmission over IP networks.
|
E1281752
|
NE FINISHED |
How this triple was built (4 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.38 | Statement: [ITU-T Study Group 16, standardized, T.38]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: T.38 Context triple: [ITU-T Study Group 16, standardized, T.38]
-
A.
T.30
T.30 is an ITU-T recommendation that defines the procedures and protocols for establishing and managing Group 3 fax communications over the public switched telephone network.
-
B.
T-68
The T-68 was an early generation light rail tram used on the Manchester Metrolink system in the UK before being superseded by newer models.
-
C.
T-29
T-29 is a U.S. Air Force military trainer aircraft variant of the Convair 240 series used primarily for navigation and radar training.
-
D.
Type 38 rifle
The Type 38 rifle was a bolt-action service rifle of the Imperial Japanese military, known for its reliability, long service life, and use throughout the early 20th century including both World Wars.
-
E.
R38
R38 is the pennant number assigned to HMS Victorious, a British Royal Navy aircraft carrier that served prominently during and after World War II.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: T.38 Triple: [ITU-T Study Group 16, standardized, T.38]
Generated description
T.38 is an ITU-T recommendation that defines a protocol for real-time fax transmission over IP networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: T.38 Target entity description: T.38 is an ITU-T recommendation that defines a protocol for real-time fax transmission over IP networks.
-
A.
T.30
T.30 is an ITU-T recommendation that defines the procedures and protocols for establishing and managing Group 3 fax communications over the public switched telephone network.
-
B.
T-68
The T-68 was an early generation light rail tram used on the Manchester Metrolink system in the UK before being superseded by newer models.
-
C.
T-29
T-29 is a U.S. Air Force military trainer aircraft variant of the Convair 240 series used primarily for navigation and radar training.
-
D.
Type 38 rifle
The Type 38 rifle was a bolt-action service rifle of the Imperial Japanese military, known for its reliability, long service life, and use throughout the early 20th century including both World Wars.
-
E.
R38
R38 is a regional commuter rail line in Catalonia that forms part of the Rodalies de Catalunya network.
- F. None of above. chosen
Provenance (5 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea469448190b2753571f8493aef |
completed | April 19, 2026, 5:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a02232075b48190a3defc74027b775e |
completed | May 11, 2026, 6:42 p.m. |
| NEDg | Description generation | batch_6a02258632d081909249af799f8d2adb |
completed | May 11, 2026, 6:52 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0225cb32c4819089ef592279cd64cb |
completed | May 11, 2026, 6:54 p.m. |
Created at: April 10, 2026, 9:39 a.m.