Triple
T6552055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest XVI. district |
E151152
|
entity |
| Predicate | isNumberedDistrictOfBudapest |
P8975
|
FINISHED |
| Object | 16 |
—
|
LITERAL FINISHED |
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: 16 | Statement: [Budapest XVI. district, isNumberedDistrictOfBudapest, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedDistrictOfBudapest Context triple: [Budapest XVI. district, isNumberedDistrictOfBudapest, 16]
-
A.
communityDistrictNumber
Indicates the specific community district identifier associated with an entity or location.
-
B.
boroughNumber
chosen
Indicates the numerical identifier assigned to a specific borough within a larger administrative or municipal division.
-
C.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
D.
hasMunicipalDistrictNumber
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
-
E.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.