Triple
T31550902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gumrak |
E804995
|
entity |
| Predicate | nearHistoricalCityName |
P76172
|
FINISHED |
| Object | Stalingrad |
—
|
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: Stalingrad | Statement: [Gumrak, nearHistoricalCityName, Stalingrad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearHistoricalCityName Context triple: [Gumrak, nearHistoricalCityName, Stalingrad]
-
A.
nearbyTownFormerName
Indicates that the nearby town previously had a different name, specifying its former name in relation to the current nearby town.
-
B.
nearbyCityFoundedBy
Indicates that a city was founded by an entity (such as a person, group, or organization) that is located near that city.
-
C.
historicalTownName
chosen
Indicates that the object is a former or historical name by which the town (subject) was previously known.
-
D.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
E.
modernLocationOfCity
Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:11 p.m.