Triple
T16354105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بین الخدماتی مخابرات |
E397128
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | ISI |
E397135
|
NE 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: ISI | Statement: [بین الخدماتی مخابرات, shortName, ISI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISI Context triple: [بین الخدماتی مخابرات, shortName, ISI]
-
A.
ISI
ISI (the Institute for Scientific Information) is a pioneering organization in bibliometrics and citation indexing, best known for creating influential tools for tracking and analyzing scientific literature.
-
B.
ISI
ISI is an organization that inspects and regulates independent schools to ensure they meet required educational and welfare standards.
-
C.
ISI
ISI is Pakistan’s premier military intelligence agency, responsible for national security intelligence and covert operations.
-
D.
I.S.I.
chosen
I.S.I. is the commonly used abbreviation for Pakistan’s premier intelligence agency, the Inter-Services Intelligence.
-
E.
ISC
ISC is an acronym commonly used to refer to an Information Security Center, an organization or unit focused on protecting information systems and data from security threats.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00355a7fb481908ed33a86c880fd49 |
completed | May 10, 2026, 7:35 a.m. |
Created at: April 10, 2026, 5:07 a.m.