Triple
T12476531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borat Sagdiyev |
E298188
|
entity |
| Predicate | hasEthnicBackgroundInFiction |
P59975
|
FINISHED |
| Object | Kazakh |
—
|
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: Kazakh | Statement: [Borat Sagdiyev, hasEthnicBackgroundInFiction, Kazakh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicBackgroundInFiction Context triple: [Borat Sagdiyev, hasEthnicBackgroundInFiction, Kazakh]
-
A.
fictionalEthnoCulturalIdentity
chosen
Indicates that an entity is associated with an invented or imaginary ethnic or cultural identity, rather than a real-world one.
-
B.
hasReputationInFiction
Indicates that an entity is known or regarded in a particular way within fictional works or narratives.
-
C.
hasFamilyNameInFiction
Indicates that a fictional character is associated with a particular family name within a work of fiction.
-
D.
hasAuthorCulturalIdentity
Indicates that an author is associated with a particular cultural identity or background.
-
E.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.