Triple
T17404585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zalaegerszeg |
E423178
|
entity |
| Predicate | hasNotableFacilityType |
P2836
|
FINISHED |
| Object | shopping centres |
—
|
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: shopping centres | Statement: [Zalaegerszeg, hasNotableFacilityType, shopping centres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFacilityType Context triple: [Zalaegerszeg, hasNotableFacilityType, shopping centres]
-
A.
hasNotableFacility
Indicates that an entity possesses or hosts a facility that is of particular significance, prominence, or interest.
-
B.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
D.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
E.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b068248819088871d79f8a38f30 |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.