Triple
T25884733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIAL |
E652154
|
entity |
| Predicate | previousCityName |
P152984
|
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: [VIAL, previousCityName, Allahabad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCityName Context triple: [VIAL, previousCityName, Allahabad]
-
A.
previousCity
Indicates that one city was the immediately preceding location visited or lived in before another city.
-
B.
previousLocationInCity
Indicates that an entity was formerly located at a specified place within a particular city before moving or changing location.
-
C.
mostRecentCity
Indicates the city in which an entity was most recently located, active, or recorded.
-
D.
predecessorCityName
chosen
Indicates that the value is the name of the city that previously held a given role, status, or position before the current city.
-
E.
formerCityName
Indicates that an entity was previously known by a different city name in the past.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 22, 2026, 8:17 a.m.