Triple
T38477566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyranny |
E915586
|
entity |
| Predicate | supportsMultipleEndings |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleEndings Context triple: [Tyranny, supportsMultipleEndings, true]
-
A.
hasEndingVariants
chosen
Indicates that an entity possesses one or more alternative forms or variations of its ending.
-
B.
hasAmbiguousEnding
Indicates that the event, story, or situation concludes in a way that is open to multiple interpretations or lacks a clear, definitive resolution.
-
C.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
D.
supportsMultipleTerminals
Indicates that an entity is capable of handling or operating with more than one terminal or endpoint simultaneously.
-
E.
supportsMultipleFiles
Indicates that the subject is capable of handling, processing, or operating on more than one file at the same time.
- F. None of above.
Provenance (1 batch)
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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.