Triple
T1254632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Mass |
E26958
|
entity |
| Predicate | typicallyCelebratedOn |
P7822
|
FINISHED |
| Object | weekdays |
—
|
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: weekdays | Statement: [Low Mass, typicallyCelebratedOn, weekdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyCelebratedOn Context triple: [Low Mass, typicallyCelebratedOn, weekdays]
-
A.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
B.
isCelebratedIn
chosen
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
-
C.
mainlyCelebratedBy
Indicates that an event, tradition, or occasion is primarily observed or celebrated by a particular group or category of people.
-
D.
seCelebraEn
Indicates that an event or occasion takes place or is held at a specific location or venue.
-
E.
relatedHoliday
Indicates that there is an association or connection between two holidays, such as thematic, temporal, cultural, or contextual relatedness.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa5a4cc819093ed686619b572d8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.