Triple
T37464368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overkill |
E930996
|
entity |
| Predicate | keywordColor |
P145753
|
FINISHED |
| Object | yellow keyword text in card rules box |
—
|
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: yellow keyword text in card rules box | Statement: [Overkill, keywordColor, yellow keyword text in card rules box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keywordColor Context triple: [Overkill, keywordColor, yellow keyword text in card rules box]
-
A.
keyTextualTheme
Indicates that one entity expresses or represents the primary textual theme or central idea associated with another entity.
-
B.
classificationColor
chosen
Indicates a relationship where an entity is assigned or associated with a specific color used for its classification or categorization.
-
C.
themeKey
Indicates that one entity serves as the primary subject, topic, or thematic focus associated with another entity.
-
D.
associatedKeyword
Indicates that one entity is linked to or characterized by a particular keyword used for identification, categorization, or retrieval.
-
E.
keyThemeIn
Indicates that a particular theme is a central or primary thematic focus within a given work, context, or subject.
- 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.