Triple
T22662718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boat Quay |
E559704
|
entity |
| Predicate | peakCommercialImportance |
P65467
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Boat Quay, peakCommercialImportance, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakCommercialImportance Context triple: [Boat Quay, peakCommercialImportance, late 19th century]
-
A.
hasCommercialImportance
Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
-
B.
portImportance
Indicates the relative significance or strategic value of a port within a given context (such as trade, logistics, or transportation networks).
-
C.
peakImportance
chosen
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
D.
commercialSignificance
Indicates that something has notable economic or business importance, value, or impact in a commercial context.
-
E.
notableCommercial
Indicates that an entity is particularly well-known or significant in a commercial context, such as advertising, marketing, or business promotion.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17660c0c88190bed9fa8f6517eec4 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.