Triple
T34439150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Archives of Estonia |
E884049
|
entity |
| Predicate | hasReadingRoomsIn |
P205433
|
FINISHED |
| Object | Tartu |
E43129
|
NE 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: Tartu | Statement: [National Archives of Estonia, hasReadingRoomsIn, Tartu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReadingRoomsIn Context triple: [National Archives of Estonia, hasReadingRoomsIn, Tartu]
-
A.
hasReadingRoom
Indicates that a place or facility includes a designated reading room area available for use.
-
B.
имеетЧитальныеЗалы
Indicates that an entity possesses or includes one or more reading rooms as part of its facilities.
-
C.
hasReadingRoomType
Indicates that an entity (such as a facility or building) has a specific type or category of reading room.
-
D.
hasReadingRoomCapacity
Indicates the maximum number of people that can be accommodated in a reading room at one time.
-
E.
hasCirculationDesk
Indicates that an entity is equipped with or contains a circulation desk, typically used for managing the lending and return of materials.
- F. None of above. chosen
Provenance (5 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729cd628881908d6a25a00e19a95e |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2 a.m.