Triple
T17200660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cos |
E417463
|
entity |
| Predicate | integratedIntoGreece |
P55609
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Cos, integratedIntoGreece, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedIntoGreece Context triple: [Cos, integratedIntoGreece, 1947]
-
A.
integratedIntoModernGreece
chosen
Indicates that a territory, region, or entity has been formally incorporated into the modern nation-state of Greece as part of its political and administrative structure.
-
B.
oneOfMajorGreekEthne
Indicates that an entity belongs to one of the primary traditional Greek ethnic groups (ethne).
-
C.
majorGreekEthnosAlongside
Indicates that one ethnic group is recognized as a major Greek ethnos existing alongside another, at a comparable level of prominence or status.
-
D.
significanceForGreece
Indicates that something holds particular importance, impact, or relevance specifically in the context of Greece.
-
E.
crossesAdministrativeRegionOfGreece
Indicates that one entity passes through or extends across the administrative region of Greece associated with 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daf2e5c81909c97d2e7a3ed7b88 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.