Triple
T25021788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastland Company |
E626594
|
entity |
| Predicate | tradePort |
P127496
|
FINISHED |
| Object | London |
—
|
NE NERFINISHED |
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: London | Statement: [Eastland Company, tradePort, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradePort Context triple: [Eastland Company, tradePort, London]
-
A.
tradeAspect
Indicates a relationship where one entity is associated with a specific aspect, feature, or dimension of a trade or commercial transaction.
-
B.
mainPortForForeignTrade
Indicates that a location serves as the primary port used for handling foreign trade activities.
-
C.
tradeBloc
Indicates a formal economic relationship in which entities participate together in a trade bloc, coordinating trade policies and often reducing barriers to commerce among members.
-
D.
tradeDestination
chosen
Indicates the location or entity to which goods, services, or financial assets are sent or directed as part of a trade transaction.
-
E.
crossBorderTradeHub
Indicates a location or entity that serves as a central point for facilitating, coordinating, or processing trade activities that occur across national or regional borders.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:06 a.m.