Triple
T62108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Day (Mexico) |
E1233
|
entity |
| Predicate | workStatus |
P127
|
FINISHED |
| Object | non-working day for many workers in Mexico |
—
|
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: non-working day for many workers in Mexico | Statement: [Independence Day (Mexico), workStatus, non-working day for many workers in Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workStatus Context triple: [Independence Day (Mexico), workStatus, non-working day for many workers in Mexico]
-
A.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another entity.
-
C.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
D.
worksOnIssue
Indicates that an entity (typically a person or team) is actively engaged in addressing, resolving, or contributing work toward a specific issue.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251f74b0881909ad89127b8171277 |
completed | Feb. 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69a24ea242c8819086fe00bf01e6523e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.