Triple
T36685484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myślewice |
E905803
|
entity |
| Predicate | usedInToponymicTraditionOf |
P20238
|
FINISHED |
| Object | Warsaw |
—
|
NE NERFINISHED |
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: Warsaw | Statement: [Myślewice, usedInToponymicTraditionOf, Warsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInToponymicTraditionOf Context triple: [Myślewice, usedInToponymicTraditionOf, Warsaw]
-
A.
usedAsToponymicBy
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
B.
hasToponymicUse
chosen
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
C.
usedAsToponymUntil
Indicates that a name or term functioned as a place name (toponym) for a location up to a specified end time or period.
-
D.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
E.
legacyToponym
Indicates that one place name is an older or former name historically used to refer to the same geographic entity as another place name.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 3, 2026, 4:12 p.m.