Triple
T37507149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Door of Shadows |
E932123
|
entity |
| Predicate | isClassAgnostic |
P189409
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Door of Shadows, isClassAgnostic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClassAgnostic Context triple: [Door of Shadows, isClassAgnostic, true]
-
A.
isClassSpecific
Indicates that something is restricted or uniquely applicable to a particular class or category, rather than being general or shared.
-
B.
isDesktopAgnostic
Indicates that something functions correctly and consistently across different desktop environments or operating systems without requiring platform-specific adaptations.
-
C.
isProtocolAgnostic
Indicates that the relationship or mechanism functions independently of any specific communication protocol, working uniformly across different protocols.
-
D.
isClass
Indicates that an entity functions as a class or type definition within a classification or type system.
-
E.
architectureAgnostic
Indicates that the relationship or action applies uniformly across different system architectures, without depending on any specific hardware or platform design.
- F. None of above. chosen
Provenance (4 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.