Triple
T37457593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsbane Rogue |
E930837
|
entity |
| Predicate | keyCard |
P186320
|
FINISHED |
| Object | Kingsbane |
—
|
NE NERFINISHED |
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: Kingsbane | Statement: [Kingsbane Rogue, keyCard, Kingsbane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCard Context triple: [Kingsbane Rogue, keyCard, Kingsbane]
-
A.
keySector
Indicates that an entity operates in, belongs to, or is primarily associated with a particularly important or strategic sector within a broader domain or economy.
-
B.
keyItem
chosen
Indicates that an item plays a crucial or required role in enabling progress, access, or completion within a given context.
-
C.
keyTown
Indicates that a town holds strategic, administrative, or economic importance within a larger region or system.
-
D.
keyCenter
Indicates the central or primary tonal focus around which other related elements are organized or interpreted.
-
E.
cardId
Indicates a relationship where an entity is associated with a specific card through its unique identifier.
- F. None of above.
Provenance (3 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.