Triple
T31589213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Eilat |
E806042
|
entity |
| Predicate | servesAsGatewayForTradeWith |
P10516
|
FINISHED |
| Object | Asia |
—
|
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: Asia | Statement: [Port of Eilat, servesAsGatewayForTradeWith, Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsGatewayForTradeWith Context triple: [Port of Eilat, servesAsGatewayForTradeWith, Asia]
-
A.
isTradedBy
Indicates that an item, asset, or resource is exchanged or dealt with by a particular agent, party, or trading entity.
-
B.
servesAsGatewayTo
chosen
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
-
C.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
D.
tradeDestination
Indicates the location or entity to which goods, services, or financial assets are sent or directed as part of a trade transaction.
-
E.
tradedUsing
Indicates that an exchange or trade was conducted by means of a specified instrument, medium, or mechanism.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: April 30, 2026, 10:27 p.m.