Triple
T26245395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The McCoys |
E656429
|
entity |
| Predicate | hasHit |
P142862
|
FINISHED |
| Object | Fever |
—
|
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: Fever | Statement: [The McCoys, hasHit, Fever]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHit Context triple: [The McCoys, hasHit, Fever]
-
A.
hasNotableHit
chosen
Indicates that an entity is associated with a particularly successful, famous, or widely recognized work, performance, or achievement.
-
B.
hitOver
Indicates that one entity strikes or impacts another entity by moving over or across it.
-
C.
wasAHitIn
Indicates that something (such as a work, product, or performance) achieved notable success or popularity within a specified context, time period, or location.
-
D.
hasMet
Indicates that one entity has encountered or come into contact with another entity at least once.
-
E.
hasReach
Indicates that one entity is able to extend its influence, access, or physical span to another entity or area.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 26, 2026, 9:05 p.m.