Triple
T28864187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesport |
E728951
|
entity |
| Predicate | supportsCluster |
P18230
|
FINISHED |
| Object | Teesside petrochemical cluster |
E728952
|
NE 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: Teesside petrochemical cluster | Statement: [Teesport, supportsCluster, Teesside petrochemical cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCluster Context triple: [Teesport, supportsCluster, Teesside petrochemical cluster]
-
A.
supportsClusterManagement
Indicates that one entity provides functionality or resources that enable the management and coordination of a cluster of related entities.
-
B.
supportsCityCluster
chosen
Indicates that one entity provides the necessary resources, infrastructure, or services for a specific city cluster to function or develop.
-
C.
hasCluster
Indicates that one entity possesses, contains, or is associated with a specific cluster or grouping of related elements.
-
D.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
E.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
- F. None of above.
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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a020ec13d808190b41acdc31adc4191 |
completed | May 11, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24bbc3fac08190a37fd1e4cc8b4907 |
completed | June 7, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_6a020d9259c08190ad0370091c23ea8a |
completed | May 11, 2026, 5:10 p.m. |
Created at: April 28, 2026, 6:48 a.m.