Triple
T31358904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of the Shades |
E799809
|
entity |
| Predicate | isSometimesPerformedAs |
P116266
|
FINISHED |
| Object | standalone excerpt |
—
|
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: standalone excerpt | Statement: [Kingdom of the Shades, isSometimesPerformedAs, standalone excerpt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSometimesPerformedAs Context triple: [Kingdom of the Shades, isSometimesPerformedAs, standalone excerpt]
-
A.
commonlyPerformedAs
Indicates that an action, behavior, or role is typically or frequently carried out in a particular manner, form, or context.
-
B.
isSometimesUsedFor
chosen
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
C.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
D.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
E.
performedUnder
Indicates that an action or task was carried out subject to, or within the scope of, a particular condition, authority, context, or framework.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f4900b88190872299a7ec7e7674 |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.