Triple
T11790291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haifa Port |
E280369
|
entity |
| Predicate | isMajorCommercialHub |
P79077
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Haifa Port, isMajorCommercialHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorCommercialHub Context triple: [Haifa Port, isMajorCommercialHub, true]
-
A.
hasMajorCityHub
Indicates that an entity contains or is associated with a primary, high-importance city that functions as a central hub for activity, services, or connectivity.
-
B.
hasMajorCommercialCentre
chosen
Indicates that a place contains or hosts a primary hub of significant commercial or business activity.
-
C.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
D.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
E.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.