Triple
T21075941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICT 1301 |
E519233
|
entity |
| Predicate | companyTypeOfUsers |
P44867
|
FINISHED |
| Object | large organizations |
—
|
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: large organizations | Statement: [ICT 1301, companyTypeOfUsers, large organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyTypeOfUsers Context triple: [ICT 1301, companyTypeOfUsers, large organizations]
-
A.
speciesOfPrimaryUser
Indicates the biological species to which the primary user of something (e.g., a device, service, or resource) belongs.
-
B.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
C.
organizationTypeServed
chosen
Indicates the type of organization that is served or supported by a given entity or activity.
-
D.
includesCompanyTypes
Indicates that a given entity encompasses or covers one or more specified categories or types of companies within its scope or definition.
-
E.
companyTypeOfDeveloper
Indicates that a given company is the type or category of organization that a particular developer belongs to or works for.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d690dc8190839968b562e6b8bb |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:48 p.m.