Triple
T6535163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Week |
E152340
|
entity |
| Predicate | workplaceEffect |
P1635
|
FINISHED |
| Object | many businesses close |
—
|
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 businesses close | Statement: [Golden Week, workplaceEffect, many businesses close]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workplaceEffect Context triple: [Golden Week, workplaceEffect, many businesses close]
-
A.
workBehavior
Indicates how an entity typically acts, performs, or conducts itself in a work or professional context.
-
B.
careerImpact
Indicates how one entity influences or changes another entity’s professional trajectory, opportunities, or outcomes.
-
C.
affectsOffice
chosen
Indicates that one entity has an influence or impact on the condition, function, or status of an office.
-
D.
focusesOnWork
Indicates that an entity directs its attention, effort, or primary activity toward work-related tasks or responsibilities.
-
E.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adc05da88190b402085954cec8e0 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.