Triple
T149071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thatcherism |
E3391
|
entity |
| Predicate | hasDebateOver |
P1783
|
FINISHED |
| Object | social inequality effects |
—
|
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: social inequality effects | Statement: [Thatcherism, hasDebateOver, social inequality effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDebateOver Context triple: [Thatcherism, hasDebateOver, social inequality effects]
-
A.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
controversy
chosen
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
D.
limitsDebateTime
Indicates that one entity imposes a restriction on the amount of time another entity is allowed to engage in debate or discussion.
-
E.
hasVoteSplit
Indicates that a collective decision or vote resulted in differing choices among participants rather than unanimous agreement.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.