Triple
T32015387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belka |
E817522
|
entity |
| Predicate | countryAssociatedWithSurname |
P15990
|
FINISHED |
| Object | Poland |
—
|
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: Poland | Statement: [Belka, countryAssociatedWithSurname, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryAssociatedWithSurname Context triple: [Belka, countryAssociatedWithSurname, Poland]
-
A.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
B.
usedAsSurnameInCountry
chosen
Indicates that a particular name functions as a family surname within the specified country.
-
C.
surnameLikelyOriginRegion
Indicates the geographic region from which a person’s surname is most likely to have originated.
-
D.
surnameAssociatedWithField
Indicates that a particular surname is commonly linked or connected to a specific professional, academic, or activity-related field.
-
E.
associatedWithNationality
Indicates that one entity has a connection or affiliation with the nationality of 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 1, 2026, 12:16 a.m.