Triple
T37462787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonehill Defender |
E930959
|
entity |
| Predicate | typicalArchetypes |
—
|
GENERATED |
| Object | control decks |
—
|
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: typicalArchetypes Context triple: [Stonehill Defender, typicalArchetypes, control decks]
-
A.
usesCharacterArchetype
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
D.
archetypeFamily
Indicates a relationship where one entity serves as a foundational or prototypical model for a family or group of related entities.
-
E.
typicalFigure
chosen
Indicates that one entity serves as a standard or representative example (a typical instance) of the other entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.