Triple
T31714546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Springs |
E809416
|
entity |
| Predicate | hasTraditionalLanguageOfName |
P21030
|
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: [Seven Springs, hasTraditionalLanguageOfName, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalLanguageOfName Context triple: [Seven Springs, hasTraditionalLanguageOfName, Greek]
-
A.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
B.
traditionalLanguageName
chosen
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
C.
hasTraditionalLanguageRegion
Indicates the geographic region traditionally associated with the use or origin of a particular language.
-
D.
hasPrimaryTraditionalLanguage
Indicates that one entity is the main or principal traditional language associated with another entity.
-
E.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: April 30, 2026, 11:16 p.m.