Triple
T33379735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bihar |
E854737
|
entity |
| Predicate | hasMajorCityHistorical |
P98392
|
FINISHED |
| Object | Nagyvárad |
—
|
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: Nagyvárad | Statement: [Bihar, hasMajorCityHistorical, Nagyvárad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorCityHistorical Context triple: [Bihar, hasMajorCityHistorical, Nagyvárad]
-
A.
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.
-
B.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
C.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
D.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
E.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00d8ba18808190976682088a02a9a8 |
completed | May 10, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a00d85fad64819084f424ec8ecd3b57 |
completed | May 10, 2026, 7:11 p.m. |
Created at: May 1, 2026, 1:35 a.m.