Triple
T29305889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windischgraz |
E743092
|
entity |
| Predicate | referencedPlaceType |
P16688
|
FINISHED |
| Object | municipality center |
—
|
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: municipality center | Statement: [Windischgraz, referencedPlaceType, municipality center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencedPlaceType Context triple: [Windischgraz, referencedPlaceType, municipality center]
-
A.
placeType
chosen
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
B.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
-
C.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
D.
connectsTypeOfPlace
Indicates a relationship where one place is linked or associated with another based on its type or category of location.
-
E.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 1:13 p.m.