Triple
T22653728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindoo Holiday |
E559163
|
entity |
| Predicate | describesTimeAs |
P2325
|
FINISHED |
| Object | holiday in India |
—
|
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: holiday in India | Statement: [Hindoo Holiday, describesTimeAs, holiday in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesTimeAs Context triple: [Hindoo Holiday, describesTimeAs, holiday in India]
-
A.
timeDescribedAs
chosen
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
B.
timeToSentence
Indicates the amount of time that elapses from a relevant starting point (e.g., offense, arrest, or charge) until a formal sentence is imposed.
-
C.
timeNotation
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
D.
representsTimeIn
Indicates that one entity expresses, encodes, or specifies the time at which another entity occurs, is valid, or is observed.
-
E.
depictionOfTime
Indicates that one entity visually represents or symbolizes a specific moment, period, or progression of time associated with 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17659e4dc81909cf6943c1c986ef9 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.