Triple
T22784494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man's Fate (stage adaptations) |
E563927
|
entity |
| Predicate | typicalSettingElement |
P116836
|
FINISHED |
| Object | Shanghai streets |
—
|
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: Shanghai streets | Statement: [Man's Fate (stage adaptations), typicalSettingElement, Shanghai streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSettingElement Context triple: [Man's Fate (stage adaptations), typicalSettingElement, Shanghai streets]
-
A.
typicalSettingConsumed
Indicates the usual context or environment in which something is normally consumed.
-
B.
typicalDesignElement
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
C.
hasFictionalSettingElement
chosen
Indicates that something includes or is associated with a specific element or component of a fictional setting.
-
D.
portrayedInSetting
Indicates that an entity is depicted or represented within a particular setting, environment, or context.
-
E.
typicalStructuralElement
Indicates that one entity is a standard or characteristic structural component commonly found within or forming part 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2f9ba48190996b4c3926728c03 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.