Triple
T21685864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tajik culture |
E535226
|
entity |
| Predicate | sharedHeritageWith |
P11721
|
FINISHED |
| Object | Iranian culture |
—
|
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: Iranian culture | Statement: [Tajik culture, sharedHeritageWith, Iranian culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedHeritageWith Context triple: [Tajik culture, sharedHeritageWith, Iranian culture]
-
A.
sharesTraditionsWith
chosen
Indicates that two entities have customs, practices, or cultural traditions in common or mutually observe similar traditional activities.
-
B.
combinesHeritageOf
Indicates a relationship where one entity integrates or unites the cultural, ancestral, or historical heritage of two or more other entities into a combined whole.
-
C.
heritageFor
Indicates that something serves as a source, basis, or contributing legacy for another entity’s heritage or tradition.
-
D.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
E.
sharesWorldHeritageListingWith
Indicates that two entities are both designated as UNESCO World Heritage Sites under the same listing or inscription.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cb69f081908ed0c7ebea429898 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.