Triple
T26783582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsi Gujarati |
E670316
|
entity |
| Predicate | culturalRoot |
P112778
|
FINISHED |
| Object | Gujarati 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: Gujarati culture | Statement: [Parsi Gujarati, culturalRoot, Gujarati culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalRoot Context triple: [Parsi Gujarati, culturalRoot, Gujarati culture]
-
A.
hasCulturalRoots
chosen
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
B.
culturalIdentifier
Indicates that one entity serves as a marker, label, or attribute that identifies or characterizes the cultural affiliation, background, or context of another entity.
-
C.
culturalRegister
Indicates the level or type of formality, style, or social context in which language or behavior is used or appropriate.
-
D.
culturalFoundationFor
Indicates that one entity provides the cultural basis, background, or supporting context that underlies or enables another entity.
-
E.
centralToCultureOf
Indicates that something is a core, defining, and influential element within the culture of a particular group or society.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 4:11 a.m.