Triple
T37650753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rondo Daszyńskiego |
E937164
|
entity |
| Predicate | isNamedLocationIn |
P188564
|
FINISHED |
| Object | city of Warsaw |
—
|
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: city of Warsaw | Statement: [Rondo Daszyńskiego, isNamedLocationIn, city of Warsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedLocationIn Context triple: [Rondo Daszyńskiego, isNamedLocationIn, city of Warsaw]
-
A.
isNamedLocation
Indicates that an entity is a specific, identifiable place referred to by a proper name.
-
B.
isNamedPlaceInGazetteer
Indicates that a place is recorded as a named geographic location within a specific gazetteer or official place-name registry.
-
C.
isNamedStandAt
Indicates that a stand (e.g., a booth, stall, or display) is located at and identified by a specific name at a given place or position.
-
D.
isNamedPublicSpaceOf
Indicates that a public space (such as a park, square, or street) bears the name associated with a particular entity (such as a person, event, or organization).
-
E.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
- F. None of above. chosen
Provenance (4 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.