Triple
T8050894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stronger In Europe |
E187668
|
entity |
| Predicate | issueEmphasis |
P17414
|
FINISHED |
| Object | economic benefits of EU membership |
—
|
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: economic benefits of EU membership | Statement: [Stronger In Europe, issueEmphasis, economic benefits of EU membership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueEmphasis Context triple: [Stronger In Europe, issueEmphasis, economic benefits of EU membership]
-
A.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
-
B.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
C.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
D.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
E.
issuesTitle
Indicates that an entity formally grants or assigns an official title or designation to another entity.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f799d1481909c91039941af0e34 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.