Triple
T31609091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton Hansen Tammsaare (symbolic grave) |
E806575
|
entity |
| Predicate | hasAssociatedPersonNationality |
P33828
|
FINISHED |
| Object | Estonian |
—
|
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: Estonian | Statement: [Anton Hansen Tammsaare (symbolic grave), hasAssociatedPersonNationality, Estonian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedPersonNationality Context triple: [Anton Hansen Tammsaare (symbolic grave), hasAssociatedPersonNationality, Estonian]
-
A.
associatedWithNationality
chosen
Indicates that one entity has a connection or affiliation with the nationality of another entity.
-
B.
hasNationalityRecord
Indicates that there exists an official record documenting an entity's nationality or national affiliation.
-
C.
hasParticipantNationality
Indicates that a participant in an event, activity, or relation has a specific nationality.
-
D.
isByNationality
Indicates that one entity has a specified nationality or originates from the country represented by the other entity.
-
E.
appliesToPersonNationality
Indicates that something is relevant or applicable specifically to a person’s nationality.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 30, 2026, 10:36 p.m.