Triple
T8472340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iDEN |
E200308
|
entity |
| Predicate | supportsCallSetup |
P83516
|
FINISHED |
| Object | fast call setup for PTT |
—
|
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: fast call setup for PTT | Statement: [iDEN, supportsCallSetup, fast call setup for PTT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCallSetup Context triple: [iDEN, supportsCallSetup, fast call setup for PTT]
-
A.
supportsCallSign
Indicates that one entity is capable of recognizing, handling, or operating using a specified call sign.
-
B.
supportsHandoverWith
Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
-
C.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
D.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
-
E.
supportsEsim
Indicates that one entity provides compatibility with, or the ability to use, an embedded SIM (eSIM) for another entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:11 p.m.