Triple
T1740872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Day |
E38228
|
entity |
| Predicate | typicalIssues |
P12230
|
FINISHED |
| Object | minimum wage |
—
|
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: minimum wage | Statement: [May Day, typicalIssues, minimum wage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIssues Context triple: [May Day, typicalIssues, minimum wage]
-
A.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
B.
facingIssue
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
-
C.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
D.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.