Triple
T37457620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsbane Rogue |
E930837
|
entity |
| Predicate | requiresCard |
P95723
|
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, requiresCard, Kingsbane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCard Context triple: [Kingsbane Rogue, requiresCard, Kingsbane]
-
A.
cardRequiredFor
chosen
Indicates that a specific card must be presented or possessed in order to access, use, or complete the related item, service, or action.
-
B.
requiresCreditAs
Indicates that one entity must be credited or acknowledged in a specified manner or role in relation to another entity.
-
C.
usesCard
Indicates that an entity employs or relies on a specific card (e.g., payment, access, or identification card) to perform an action or participate in an interaction.
-
D.
creditRequired
Indicates that a certain amount or type of credit must be obtained or possessed as a prerequisite for something (such as access, participation, or completion).
-
E.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
- 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_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: May 3, 2026, 4:17 p.m.