Triple
T344765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peterloo Memorial in Manchester |
E6914
|
entity |
| Predicate | controversyTopic |
P5303
|
FINISHED |
| Object | lack of step-free access |
—
|
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: lack of step-free access | Statement: [Peterloo Memorial in Manchester, controversyTopic, lack of step-free access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controversyTopic Context triple: [Peterloo Memorial in Manchester, controversyTopic, lack of step-free access]
-
A.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
B.
frequentlyDiscussedIn
chosen
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
C.
languageOfDebate
Indicates that a specified language is the one used for conducting a particular debate.
-
D.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
E.
titleContested
Indicates that the legitimacy or ownership of a title is disputed between parties.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb01261c81909280128b5ce75eff |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.