Triple
T31014151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFP Communications, Electronics and Information Systems Service |
E790282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized service branch |
C25280
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: specialized service branch Context triple: [AFP Communications, Electronics and Information Systems Service, instanceOf, specialized service branch]
-
A.
specialized division
A specialized division is a distinct organizational unit focused on a specific function, expertise, or market segment to improve efficiency and effectiveness within a larger entity.
-
B.
specialist corps
A specialist corps is a dedicated group of highly trained experts within a larger organization or system, formed to perform complex, technical, or niche tasks that require advanced, domain-specific skills.
-
C.
specialized civil service
A specialized civil service is a segment of the public administration composed of professionals with specific technical or sectoral expertise who perform defined governmental functions under merit-based rules and career structures.
-
D.
specialized branch library
A specialized branch library is a smaller, focused extension of a main library system that concentrates on a particular subject area, user group, or service type while providing targeted collections and expertise.
-
E.
specialist unit
chosen
A specialist unit is a dedicated organizational subgroup composed of experts and specialized resources focused on performing specific, complex, or high-priority tasks within a broader system or institution.
- F. None of above.
Provenance (1 batch)
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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.