Triple
T27963542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cenchreae |
E704652
|
entity |
| Predicate | oppositePort |
P44148
|
FINISHED |
| Object | Lechaeum |
E419468
|
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: Lechaeum | Statement: [Cenchreae, oppositePort, Lechaeum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositePort Context triple: [Cenchreae, oppositePort, Lechaeum]
-
A.
neighboringPort
Indicates that two ports are geographically close to each other, typically sharing a boundary or lying within a short distance along a coast or waterway.
-
B.
sisterPortWith
Indicates that two ports are officially paired as sister ports, signifying a formal cooperative or partnership relationship between them.
-
C.
exportPort
Indicates the port or harbor from which goods, resources, or data are sent out from one location or entity to another.
-
D.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
E.
oppositeShoreFrom
chosen
Indicates that two locations are situated on facing sides of the same body of water or shoreline, directly across from each other.
- F. None of above.
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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a13116f3c508190b2f0f8129aaaba79 |
completed | May 24, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 7:33 p.m.