Triple
T35604350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devonport, Tasmania |
E1028843
|
entity |
| Predicate | isMajorRegionalPort |
P17488
|
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: [Devonport, Tasmania, isMajorRegionalPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorRegionalPort Context triple: [Devonport, Tasmania, isMajorRegionalPort, true]
-
A.
isMajorRegionFor
Indicates that a region serves as a primary or significant area associated with a particular entity, activity, or phenomenon.
-
B.
isMajorRegionalCenter
Indicates that a location functions as a primary hub of economic, administrative, or cultural activity within a specific geographic region.
-
C.
isRegionalPort
chosen
Indicates that a port serves primarily a specific region or local area rather than functioning as a major national or international hub.
-
D.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
-
E.
isMajorLandingRegion
Indicates that a location serves as a primary or significant area where landings (such as aircraft, spacecraft, or vessels) commonly occur.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:05 p.m.