Triple
T37464352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overkill |
E930996
|
entity |
| Predicate | associatedSetType |
P205906
|
FINISHED |
| Object | expansion-specific keyword |
—
|
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: expansion-specific keyword | Statement: [Overkill, associatedSetType, expansion-specific keyword]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSetType Context triple: [Overkill, associatedSetType, expansion-specific keyword]
-
A.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
B.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
C.
associatedWithSetting
Indicates that one entity is connected or linked to a particular context, environment, or setting in which it occurs or is relevant.
-
D.
associatedEnsembleOf
Indicates that one entity is linked or connected to a particular ensemble, typically as a member, contributor, or related component of that group.
-
E.
collectivelySet
Indicates that multiple entities jointly determine or assign a value, state, or configuration together as a group rather than individually.
- 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.