Triple
T15147496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea of Thessaly (Aegean Sea coast) |
E361850
|
entity |
| Predicate | languageUsedInLocalToponymy |
P24399
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [Sea of Thessaly (Aegean Sea coast), languageUsedInLocalToponymy, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInLocalToponymy Context triple: [Sea of Thessaly (Aegean Sea coast), languageUsedInLocalToponymy, Greek]
-
A.
hasLanguageOfToponym
chosen
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
B.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
C.
countryNameLocal
Indicates the name of a country as expressed in its own local or official language.
-
D.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
-
E.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c825a481909d00098b0e743365 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.