Triple
T8477450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phigalia |
E200430
|
entity |
| Predicate | connectedByAncientRoad |
P11435
|
FINISHED |
| Object | route to Bassae |
—
|
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: route to Bassae | Statement: [Phigalia, connectedByAncientRoad, route to Bassae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByAncientRoad Context triple: [Phigalia, connectedByAncientRoad, route to Bassae]
-
A.
linkedByRoadTo
chosen
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
B.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
-
C.
hasNearbyAncientCity
Indicates that one entity is located close to another entity that is classified as an ancient city.
-
D.
wasCrossroadsOf
Indicates that a place served as a central junction or meeting point where multiple routes, paths, or influences converged.
-
E.
locatedInAncientCity
Indicates that an entity is situated within the boundaries or domain of an ancient city.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe51ffab881908448aff899511f2c |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.