Triple
T37457481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagger Mastery |
E930834
|
entity |
| Predicate | cardId |
P187878
|
FINISHED |
| Object | CS2_083 |
—
|
LITERAL 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: CS2_083 | Statement: [Dagger Mastery, cardId, CS2_083]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardId Context triple: [Dagger Mastery, cardId, CS2_083]
-
A.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
B.
cardFunction
Indicates that one entity serves as the functional role, capability, or purpose associated with a card-related entity in a system.
-
C.
cardSegment
Indicates a relationship where a card is divided into or associated with a specific segment or portion of itself.
-
D.
cardTypeAccess
Indicates that access or permissions are determined or constrained based on the type of card involved.
-
E.
cardClass
Indicates the classification or category to which a given card belongs within a defined card system or schema.
- F. None of above. chosen
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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.