Triple
T37457581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsbane Rogue |
E930837
|
entity |
| Predicate | basedOnCard |
P192502
|
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, basedOnCard, Kingsbane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnCard Context triple: [Kingsbane Rogue, basedOnCard, Kingsbane]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
basedOnCatalogOf
Indicates that something is derived, defined, or constructed according to a specified catalog or standardized collection of items.
-
C.
usesCard
chosen
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.
basedOnProduct
Indicates that something is derived from, influenced by, or created using a particular product as its source or foundation.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
- 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_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: May 3, 2026, 4:17 p.m.