Triple
T27753364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mistry |
E701270
|
entity |
| Predicate | typicalCulturalAssociation |
P958
|
FINISHED |
| Object | Parsi community |
—
|
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: Parsi community | Statement: [Mistry, typicalCulturalAssociation, Parsi community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCulturalAssociation Context triple: [Mistry, typicalCulturalAssociation, Parsi community]
-
A.
traditionAssociatesWith
Indicates that a particular tradition is connected or linked to another entity, such as a practice, group, place, or concept.
-
B.
hasCulturalSignificanceFor
chosen
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
C.
materialCultureAssociation
Indicates an association between entities based on shared or related material culture, such as artifacts, objects, or physical cultural items.
-
D.
culturalIdentityTiedTo
Indicates that an entity’s cultural identity is closely connected or strongly associated with another specified entity or context.
-
E.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: April 27, 2026, 4:21 p.m.