Triple
T30506824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football Club Zenit |
E776296
|
entity |
| Predicate | cityPreviouslyKnownAs |
P69706
|
FINISHED |
| Object | Leningrad |
—
|
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: Leningrad | Statement: [Football Club Zenit, cityPreviouslyKnownAs, Leningrad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityPreviouslyKnownAs Context triple: [Football Club Zenit, cityPreviouslyKnownAs, Leningrad]
-
A.
cityThenKnownAs
Indicates that an entity had a particular city name during a specified earlier time period, before it was renamed or became known by a different name.
-
B.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
C.
formerCityName
chosen
Indicates that an entity was previously known by a different city name in the past.
-
D.
formerNameOfCapital
Indicates that one entity was the previous official name of a capital city before it was renamed.
-
E.
nearbyTownFormerName
Indicates that the nearby town previously had a different name, specifying its former name in relation to the current nearby town.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687b4dddc8190a59fd13d2f8a2e16 |
completed | May 2, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:15 p.m.