Triple
T33607676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11,000 Virgins |
E860903
|
entity |
| Predicate | hasRelicTraditionIn |
—
|
GENERATED |
| Object | Cologne |
—
|
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: hasRelicTraditionIn Context triple: [11,000 Virgins, hasRelicTraditionIn, Cologne]
-
A.
hasRelicType
Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
-
B.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
C.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
-
D.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
E.
hasStatusInTradition
Indicates that an entity holds a particular recognized status or standing within a specified tradition or traditional framework.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.