Triple
T32546383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Χερσόνησος του Άθω |
E831857
|
entity |
| Predicate | έχειΠεριορισμούςΠρόσβασης |
P9584
|
FINISHED |
| Object | απαγόρευση εισόδου στις γυναίκες (άβατο) |
—
|
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: απαγόρευση εισόδου στις γυναίκες (άβατο) | Statement: [Χερσόνησος του Άθω, έχειΠεριορισμούςΠρόσβασης, απαγόρευση εισόδου στις γυναίκες (άβατο)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: έχειΠεριορισμούςΠρόσβασης Context triple: [Χερσόνησος του Άθω, έχειΠεριορισμούςΠρόσβασης, απαγόρευση εισόδου στις γυναίκες (άβατο)]
-
A.
έχειΜεταγραφή
Indicates that an entity has been transferred or has undergone a transfer (e.g., between organizations, teams, or systems).
-
B.
έχειΠλάτος
Indicates that an entity possesses or is characterized by a certain width.
-
C.
έχειΚατηγοριοποιηθείΩς
Indicates that an entity has been classified or assigned to a specific category or type.
-
D.
έχειΘέα
Indicates that one entity offers or provides a view of, or overlooking, another entity.
-
E.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.