Triple
T25059362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antirrio |
E627612
|
entity |
| Predicate | oppositeSideOfStraitFrom |
P44148
|
FINISHED |
| Object | Peloponnese |
—
|
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: Peloponnese | Statement: [Antirrio, oppositeSideOfStraitFrom, Peloponnese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeSideOfStraitFrom Context triple: [Antirrio, oppositeSideOfStraitFrom, Peloponnese]
-
A.
bodyOfWaterOnOtherSide
Indicates that one entity is located across a body of water from the other entity, with the water lying between them.
-
B.
separatedByOceanFrom
Indicates that two entities are located on different landmasses with an ocean lying between them as a separating barrier.
-
C.
oppositeShoreFrom
chosen
Indicates that two locations are situated on facing sides of the same body of water or shoreline, directly across from each other.
-
D.
isNorthernmostStraitOf
Indicates that one strait is the furthest north among all straits associated with a particular geographic feature or region.
-
E.
oppositeContinent
Indicates that two entities are located on continents that are considered opposites of each other, typically in terms of global position or conceptual pairing.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45997ff78819082a60f81f9a88064 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:09 a.m.