Triple
T30929057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raekoja plats |
E787938
|
entity |
| Predicate | isSocialHubOf |
P43434
|
FINISHED |
| Object | Tartu |
—
|
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: Tartu | Statement: [Raekoja plats, isSocialHubOf, Tartu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSocialHubOf Context triple: [Raekoja plats, isSocialHubOf, Tartu]
-
A.
socialMediaPlatformAssociatedWith
Indicates that there is an association or linkage between an entity and a specific social media platform.
-
B.
socialCenter
chosen
Indicates that a place functions as a primary gathering point or hub for social interaction and community activities.
-
C.
sociallyIntegratedWith
Indicates that two entities are connected through meaningful social relationships, interactions, or participation within the same social context or community.
-
D.
isITHubOf
Indicates that an entity serves as a central location or primary center for IT-related activities, services, or operations for another entity or area.
-
E.
socialSphere
Indicates the social environment or network within which an entity regularly interacts or maintains relationships.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692df4c0c8190807c821ac7d0e09b |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:52 p.m.