Triple
T24043491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makoto |
E595452
|
entity |
| Predicate | isUsedByCulture |
P7826
|
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: [Makoto, isUsedByCulture, Japanese culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedByCulture Context triple: [Makoto, isUsedByCulture, Japanese culture]
-
A.
usedCulture
Indicates that one entity employed, applied, or drew upon the cultural practices, norms, or artifacts associated with another entity.
-
B.
usedInCulture
chosen
Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
-
C.
isCulturalLanguageOf
Indicates that a language serves as a primary medium of cultural expression, identity, and heritage for a particular group, community, or region.
-
D.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
E.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8db3b4c81908a36eace8ec136cc |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:04 p.m.