Triple
T35629539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Mersin |
E1029545
|
entity |
| Predicate | servesTrade |
P201724
|
FINISHED |
| Object | international 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: international trade | Statement: [Port of Mersin, servesTrade, international trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTrade Context triple: [Port of Mersin, servesTrade, international trade]
-
A.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
B.
servesProduct
Indicates that one entity provides or offers a particular product to others, typically in a commercial or service context.
-
C.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
D.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs of another entity.
-
E.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_6a0018cebf688190bbd90ac79d250182 |
completed | May 10, 2026, 5:34 a.m. |
Created at: May 3, 2026, 4:05 p.m.