Triple
T38010358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Blackpool |
E948346
|
entity |
| Predicate | refusesToJoin |
P189853
|
FINISHED |
| Object | trade union |
—
|
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: trade union | Statement: [Stephen Blackpool, refusesToJoin, trade union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusesToJoin Context triple: [Stephen Blackpool, refusesToJoin, trade union]
-
A.
refusesToLeave
Indicates that an entity is unwilling to depart from a place, situation, or state despite expectation or pressure to do so.
-
B.
refusesHelpFrom
Indicates that one entity declines or rejects assistance offered by another entity.
-
C.
refusesToSatisfy
Indicates a situation where one entity deliberately declines or withholds fulfilling another entity’s request, demand, or requirement.
-
D.
refusedAllegianceTo
Indicates that one entity declined or rejected giving loyalty, support, or obedience to another entity.
-
E.
refusedToAbdicate
Indicates that a person who holds power or authority declined to give up or renounce their position when expected or requested to do so.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.