Triple
T37464343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overkill |
E930996
|
entity |
| Predicate | hasExampleCard |
P188366
|
FINISHED |
| Object | Baited Arrow |
—
|
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: Baited Arrow | Statement: [Overkill, hasExampleCard, Baited Arrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExampleCard Context triple: [Overkill, hasExampleCard, Baited Arrow]
-
A.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
B.
cardExample
chosen
Indicates that something is an illustrative or sample instance of a card (such as a prototype, demo, or example card) rather than a primary or production card.
-
C.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
-
D.
hasBasicCardSet
Indicates that an entity is associated with or includes a fundamental or default set of cards.
-
E.
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.
- 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:17 p.m.