Triple
T24054669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prayagraj metropolitan area |
E595763
|
entity |
| Predicate | historicalNameOfCoreCity |
P76172
|
FINISHED |
| Object | Allahabad |
—
|
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: Allahabad | Statement: [Prayagraj metropolitan area, historicalNameOfCoreCity, Allahabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameOfCoreCity Context triple: [Prayagraj metropolitan area, historicalNameOfCoreCity, Allahabad]
-
A.
historicalNameOfCityOnRiver
Indicates that a given name is a historical name of a city that is (or was) located on a particular river.
-
B.
formerNameOfCapital
Indicates that one entity was the previous official name of a capital city before it was renamed.
-
C.
historicalTownName
chosen
Indicates that the object is a former or historical name by which the town (subject) was previously known.
-
D.
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.
-
E.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d551288190a2b3b6c8c4f3c1b5 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:22 p.m.