Triple
T9183135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rozenburg |
E220384
|
entity |
| Predicate | hasPortRelatedIndustry |
P53279
|
FINISHED |
| Object | petrochemical industry |
—
|
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: petrochemical industry | Statement: [Rozenburg, hasPortRelatedIndustry, petrochemical industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortRelatedIndustry Context triple: [Rozenburg, hasPortRelatedIndustry, petrochemical industry]
-
A.
containsIndustry
chosen
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
B.
hasNearbyIndustry
Indicates that an entity is located close to one or more industrial facilities or activities.
-
C.
hasParentCompanyIndustry
Indicates that an entity’s parent company operates in, or is associated with, a specified industry.
-
D.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
E.
relationToIndustry
Indicates how an entity is connected or relevant to a particular industry, such as through involvement, impact, or association.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc2553e548190898434aeda517407 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.