Triple
T2214676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labor Day weekend |
E47997
|
entity |
| Predicate | workPattern |
P36842
|
FINISHED |
| Object | many workers have Monday off |
—
|
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: many workers have Monday off | Statement: [Labor Day weekend, workPattern, many workers have Monday off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPattern Context triple: [Labor Day weekend, workPattern, many workers have Monday off]
-
A.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
C.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
D.
workSettingPeriod
Indicates the time period during which a particular work setting or employment context is in effect.
-
E.
workModel
Indicates that one entity serves as, or is based on, a particular model used for work, operation, or functional behavior.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbfef875c8190b642736b4cc11d4c |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf0c2b8881908553eed5be17a9c2 |
completed | March 7, 2026, 6 a.m. |
Created at: March 4, 2026, 7:46 p.m.