Triple
T33568157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axios–Loudias–Aliakmonas National Park |
E859815
|
entity |
| Predicate | containsRiverDelta |
P19477
|
FINISHED |
| Object | Axios River |
—
|
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: Axios River | Statement: [Axios–Loudias–Aliakmonas National Park, containsRiverDelta, Axios River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRiverDelta Context triple: [Axios–Loudias–Aliakmonas National Park, containsRiverDelta, Axios River]
-
A.
locatedInRiverDelta
Indicates that one entity is situated within the river delta region of another entity (the river).
-
B.
hasMajorRiverDelta
chosen
Indicates that a geographic region or water body possesses a significant river delta formed by sediment deposition at or near its mouth.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
hasMajorCityOnRiver
Indicates that a major city is located on and directly associated with a particular river.
-
E.
hasCityOnRiver
Indicates that a city is located on or along the course of a particular river.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:40 a.m.