Triple
T35211780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creüsa |
E1016697
|
entity |
| Predicate | cityAssociatedWithOffspring |
P22410
|
FINISHED |
| Object | Ionian cities |
—
|
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: Ionian cities | Statement: [Creüsa, cityAssociatedWithOffspring, Ionian cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityAssociatedWithOffspring Context triple: [Creüsa, cityAssociatedWithOffspring, Ionian cities]
-
A.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
B.
birthPlaceOfChildren
chosen
Indicates the location where a person's children were born.
-
C.
hasHometownOf
Indicates that one entity has, as its hometown, the place represented by the other entity.
-
D.
isBirthplaceRelatedTo
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
-
E.
isNamesakeHomeOf
Indicates that a place serves as the home or primary location associated with the person, entity, or concept for which it is named.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.