Triple
T37515091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templar |
E932613
|
entity |
| Predicate | supportsBuildArchetype |
—
|
GENERATED |
| Object | totem builds |
—
|
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: supportsBuildArchetype Context triple: [Templar, supportsBuildArchetype, totem builds]
-
A.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
B.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
C.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
D.
supportsBuildManagement
chosen
Indicates that one entity provides functionality or assistance for managing the build process of another entity (such as compiling, packaging, and related build tasks).
-
E.
hasArchitecturalSupport
Indicates that one entity provides structural or design backing, compatibility, or enablement for another within an architectural context.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.