Triple
T14864254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krisztinaváros |
E349576
|
entity |
| Predicate | streetNetworkEra |
P115933
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Krisztinaváros, streetNetworkEra, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNetworkEra Context triple: [Krisztinaváros, streetNetworkEra, 19th century]
-
A.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
B.
streetNetworkIncludes
Indicates that a given street network contains or encompasses a specified street segment, feature, or component as part of its structure.
-
C.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
D.
trailNetworkType
Indicates the classification of a trail within a broader trail network, such as its role, category, or type of route in that system.
-
E.
hasHistoricStreet
Indicates that an entity is associated with or located on a street that has recognized historical significance.
- F. None of above. chosen
Provenance (4 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded574d0ec8190a6afed672ba6c2f9 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.