Triple
T21661950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi Kayan |
E534614
|
entity |
| Predicate | hasMainOperations |
P144902
|
FINISHED |
| Object | production of basic chemicals |
—
|
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: production of basic chemicals | Statement: [Saudi Kayan, hasMainOperations, production of basic chemicals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainOperations Context triple: [Saudi Kayan, hasMainOperations, production of basic chemicals]
-
A.
hasOperationsIn
Indicates that an entity conducts business activities or maintains operational presence within a specified location or region.
-
B.
hasGlobalOperationsIn
Indicates that an entity conducts business or operational activities across multiple countries within the specified region or location.
-
C.
hasGlobalOperations
Indicates that an entity conducts its activities or services across multiple countries or worldwide.
-
D.
hasMainOperatorFlagState
Indicates that an entity’s primary operator is associated with, or currently in, a specific flag-defined state.
-
E.
hasMajorOperator
Indicates that an entity is primarily operated, managed, or run by a specified main operator or organization.
- F. None of above. chosen
Provenance (4 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c0883d481908dfdc66832c34d74 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:36 p.m.