Triple
T38110626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galakrond, the Wretched |
E951643
|
entity |
| Predicate | hasRelatedCardCycle |
P43666
|
FINISHED |
| Object | Galakrond cycle |
E2228518
|
NE 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: Galakrond cycle | Statement: [Galakrond, the Wretched, hasRelatedCardCycle, Galakrond cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedCardCycle Context triple: [Galakrond, the Wretched, hasRelatedCardCycle, Galakrond cycle]
-
A.
hasCardAssociation
Indicates that there is an established relationship or linkage between an entity and a specific card or card-related system.
-
B.
belongsToCycle
chosen
Indicates that an entity is part of, or contained within, a specific cycle or cyclic structure.
-
C.
hasCardinal
Indicates that something possesses or is associated with a specific cardinal number or quantity.
-
D.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
-
E.
associatedKeyOfCycle
Indicates a relationship where a key is linked to or derived from a specific cycle within a process, structure, or system.
- F. None of above.
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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41681a04788190853f20b30617403e |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.