Triple
T32080367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soryu |
E819275
|
entity |
| Predicate | presentInCulture |
P180705
|
FINISHED |
| Object | Japanese mythology |
—
|
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 mythology | Statement: [Soryu, presentInCulture, Japanese mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentInCulture Context triple: [Soryu, presentInCulture, Japanese mythology]
-
A.
hasCulturalPresenceOf
chosen
Indicates that something exhibits, contains, or is characterized by the cultural influence, activities, or representation of a particular group, tradition, or culture.
-
B.
usedInCulture
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.
hasCulturalDepiction
Indicates that one entity is represented, portrayed, or depicted in the cultural work or expression of another entity.
-
D.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
E.
collectionIncludesCulture
Indicates that a collection contains, represents, or is associated with 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:24 a.m.