Triple
T4995429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West India Docks |
E112233
|
entity |
| Predicate | primaryTrade |
P61379
|
FINISHED |
| Object | West Indies trade |
—
|
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: West Indies trade | Statement: [West India Docks, primaryTrade, West Indies trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTrade Context triple: [West India Docks, primaryTrade, West Indies trade]
-
A.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
B.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
C.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
D.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
E.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd74713fc88190916c2b04cd2e677e |
completed | March 20, 2026, 4:23 p.m. |
Created at: March 20, 2026, 1:34 p.m.