Triple
T26718024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amata City Industrial Estate |
E673619
|
entity |
| Predicate | servesCompanyType |
P44867
|
FINISHED |
| Object | multinational corporations |
—
|
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: multinational corporations | Statement: [Amata City Industrial Estate, servesCompanyType, multinational corporations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCompanyType Context triple: [Amata City Industrial Estate, servesCompanyType, multinational corporations]
-
A.
servesCompany
Indicates that one entity provides services or performs duties in support of a company.
-
B.
includesCompanyTypes
Indicates that a given entity encompasses or covers one or more specified categories or types of companies within its scope or definition.
-
C.
organizationTypeServed
chosen
Indicates the type of organization that is served or supported by a given entity or activity.
-
D.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
E.
representsCompanyType
Indicates that an entity is associated with or classified under a specific type or category of company.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 27, 2026, 3:39 a.m.