Triple
T15879106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akkō |
E385026
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Acre Port |
E947155
|
NE 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: Acre Port | Statement: [Akkō, hasPart, Acre Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Acre Port Context triple: [Akkō, hasPart, Acre Port]
-
A.
Acre port
chosen
Acre port is a historic Mediterranean harbor in the city of Acre (Akko) in present-day Israel, long significant as a strategic maritime gateway for trade and military campaigns.
-
B.
Mwanza Port
Mwanza Port is a major Tanzanian inland port on Lake Victoria that serves as a key hub for regional transport and trade in the Mwanza area.
-
C.
Acre harbor
Acre harbor is the historic port of the ancient city of Acre (Akko) on Israel’s Mediterranean coast, long serving as a strategic maritime hub for trade and naval activity.
-
D.
Onsan Port
Onsan Port is a major industrial seaport in Ulsan, South Korea, serving as a key logistics hub for nearby heavy and petrochemical industries.
-
E.
Lindi Port
Lindi Port is a coastal seaport in southeastern Tanzania that serves as a regional maritime hub for the Lindi area on the Indian Ocean.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e155ff96588190b8fca1c3bf4a39a2 |
completed | April 16, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb59f979c8190826e35a16e295704 |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 4:51 a.m.