Triple
T32277681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Iranians |
E824597
|
entity |
| Predicate | hostCountryCulture |
P97639
|
FINISHED |
| Object | British 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: British culture | Statement: [British Iranians, hostCountryCulture, British culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCountryCulture Context triple: [British Iranians, hostCountryCulture, British culture]
-
A.
basedInCulture
chosen
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
B.
cultureOfOrigin
Indicates the cultural background or tradition from which an entity originates or is derived.
-
C.
hostNationality
Indicates the national affiliation or citizenship of the host in a given hosting relationship or context.
-
D.
centralToCultureOf
Indicates that something is a core, defining, and influential element within the culture of a particular group or society.
-
E.
usesCulture
Indicates that one entity employs, incorporates, or relies on the cultural practices, norms, or artifacts associated with another entity in its actions or functioning.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:43 a.m.