Triple
T17133460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Tainaron |
E415776
|
entity |
| Predicate | hasAncientNameLanguage |
P52208
|
FINISHED |
| Object | Ancient 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: Ancient Greek | Statement: [Cape Tainaron, hasAncientNameLanguage, Ancient Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncientNameLanguage Context triple: [Cape Tainaron, hasAncientNameLanguage, Ancient Greek]
-
A.
hasAncientEthnicName
Indicates that an entity is associated with an ethnic name or designation that originates from ancient times.
-
B.
languageOfHistoricName
chosen
Indicates the language in which a historic or former name of an entity is expressed.
-
C.
hasModernNameLanguage
Indicates that the modern name of an entity is expressed in a particular language.
-
D.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
E.
hasNamesakeLanguage
Indicates that an entity has a language named after it or sharing the same name as the 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02cbb7881908aa69c3443d149d5 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.