Triple
T38582638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zandalar |
E932277
|
entity |
| Predicate | notableLoa |
—
|
GENERATED |
| Object | Rezan |
—
|
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: notableLoa Context triple: [Zandalar, notableLoa, Rezan]
-
A.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
B.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
C.
notableTrustee
Indicates that the subject serves or has served as a distinguished or prominent trustee of the object (such as an organization or institution).
-
D.
notableStandard
Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
-
E.
notablePass
Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
- F. None of above. chosen
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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.