Triple
T15251731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dejima trading post |
E364532
|
entity |
| Predicate | languageOfTrade |
P74986
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [Dejima trading post, languageOfTrade, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfTrade Context triple: [Dejima trading post, languageOfTrade, Dutch]
-
A.
languageUsedInTrade
chosen
Indicates that a particular language is employed as a medium of communication in trade or commercial transactions between parties.
-
B.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
languageOfNegotiation
Indicates that a specified language is used as the medium of communication during a negotiation between parties.
-
D.
languageOfPrimaryMarkets
Indicates the primary language or languages used in the main markets where an entity operates or targets its products or services.
-
E.
languageOfOperator
Indicates that a particular language is used by, or associated with, a given operator in performing its functions or services.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f728648190b2c86e4528542b65 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.