Triple
T16518476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Silver Lotus |
E401249
|
entity |
| Predicate | hasMainSettingCulture |
P1439
|
FINISHED |
| Object | Eastern world |
—
|
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: Eastern world | Statement: [The Silver Lotus, hasMainSettingCulture, Eastern world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSettingCulture Context triple: [The Silver Lotus, hasMainSettingCulture, Eastern world]
-
A.
hasCustomizationCulture
Indicates that one entity fosters or embodies a culture, practice, or norm of customizing or tailoring products, services, or experiences for another entity.
-
B.
hasMainCult
Indicates that an entity is associated with a primary or predominant cult or religious worship tradition.
-
C.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
D.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
E.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7ec45c8190b5e2c4a5f707e332 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.