Triple
T34845257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobu |
E1004446
|
entity |
| Predicate | isNameElementInCulture |
P99146
|
FINISHED |
| Object | Japanese 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: Japanese culture | Statement: [Nobu, isNameElementInCulture, Japanese culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNameElementInCulture Context triple: [Nobu, isNameElementInCulture, Japanese culture]
-
A.
isGivenNameInCulture
chosen
Indicates that a particular given (first) name is used or recognized within a specified culture or cultural context.
-
B.
isCulturalStandardFor
Indicates that something is recognized or accepted as the customary or normative practice, value, or behavior within a particular culture or cultural context.
-
C.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
D.
hasCulturalDimensionWith
Indicates that one entity possesses or is associated with a particular cultural dimension in relation to another entity.
-
E.
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.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.