Triple
T34945037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ano Liosia |
E1007833
|
entity |
| Predicate | geographicDirectionFromAthens |
P190521
|
FINISHED |
| Object | northwestern |
—
|
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: northwestern | Statement: [Ano Liosia, geographicDirectionFromAthens, northwestern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDirectionFromAthens Context triple: [Ano Liosia, geographicDirectionFromAthens, northwestern]
-
A.
geographicalDirectionFromConstantinople
Indicates that one place is located in a specified cardinal or intercardinal direction relative to Constantinople.
-
B.
distanceFromAthens_km
Indicates the physical distance, measured in kilometers, between a given place and the city of Athens.
-
C.
distanceFromAthensBySea
Indicates the measured distance between a place and Athens when traveling via sea routes.
-
D.
directionFromThessaloniki
Indicates the cardinal or relative compass direction of an entity’s location as measured from Thessaloniki.
-
E.
distanceToAthensCenter
Indicates the spatial distance between a given location and the center of Athens.
- F. None of above. chosen
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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4 p.m.