Triple
T17008890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldport |
E412644
|
entity |
| Predicate | hubType |
P126187
|
FINISHED |
| Object | global hub |
—
|
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: global hub | Statement: [Worldport, hubType, global hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hubType Context triple: [Worldport, hubType, global hub]
-
A.
hubFor
Indicates that one entity serves as a central node or focal point through which activities, connections, or resources related to another entity are organized or routed.
-
B.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
C.
hubHeight
Indicates the vertical distance from the ground or reference level to the central hub point of a structure or device.
-
D.
exportHubFor
Indicates that one entity serves as the primary export hub or central exporting point for another entity’s goods or services.
-
E.
repositoryType
Indicates the kind or classification of a repository associated with an entity.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d3853f548190910240a2145cc890 |
completed | April 18, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:33 a.m.