Triple
T16354107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بین الخدماتی مخابرات |
E397128
|
entity |
| Predicate | fullNameUrdu |
P14620
|
FINISHED |
| Object | بین الخدماتی مخابرات |
—
|
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: بین الخدماتی مخابرات | Statement: [بین الخدماتی مخابرات, fullNameUrdu, بین الخدماتی مخابرات]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameUrdu Context triple: [بین الخدماتی مخابرات, fullNameUrdu, بین الخدماتی مخابرات]
-
A.
hasNameInUrdu
chosen
Indicates that an entity is associated with a specific name expressed in the Urdu language.
-
B.
firstLineInUrdu
Indicates that the referenced text is the first line of a piece of content when written or displayed in Urdu.
-
C.
hasNameInPunjabi
Indicates that an entity is associated with a specific name expressed in the Punjabi language.
-
D.
nameInKurdish
Indicates that an entity is referred to by a particular name in the Kurdish language.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facd80dc8190b08f0eecbf787240 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.