Triple
T27452255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imbrasos River |
E692477
|
entity |
| Predicate | locatedInAncientPolity |
P24406
|
FINISHED |
| Object | ancient polis of Samos |
—
|
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 polis of Samos | Statement: [Imbrasos River, locatedInAncientPolity, ancient polis of Samos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInAncientPolity Context triple: [Imbrasos River, locatedInAncientPolity, ancient polis of Samos]
-
A.
locatedInAncientCity
chosen
Indicates that an entity is situated within the boundaries or domain of an ancient city.
-
B.
countryDuringAntiquity
Indicates that an entity functioned as a country or political territory specifically during the historical period of antiquity.
-
C.
ancientStates
Indicates that the related entity functioned as a state or political entity in ancient times.
-
D.
governedInAntiquityBy
Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
-
E.
usedInHistoricalPolity
Indicates that something (such as a name, title, or term) was employed or attested within the context of a specific historical polity or political 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: April 27, 2026, 12:47 p.m.