Triple
T37834980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upland Hungary |
E943312
|
entity |
| Predicate | importantCityHistorically |
P98392
|
FINISHED |
| Object | Pressburg |
—
|
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: Pressburg | Statement: [Upland Hungary, importantCityHistorically, Pressburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantCityHistorically Context triple: [Upland Hungary, importantCityHistorically, Pressburg]
-
A.
focusCityHistory
Indicates that there is a historical or context-defining relationship between a focal city and its past events, developments, or status.
-
B.
capitalOrMajorCityHistorically
chosen
Indicates that a place has historically served as a capital or as a major, centrally important city for a political or cultural entity.
-
C.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
D.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
E.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.