Triple
T23294178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Rabbit |
E590116
|
entity |
| Predicate | associatedWithHours |
P11533
|
FINISHED |
| Object | 05:00–07:00 |
—
|
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: 05:00–07:00 | Statement: [Year of the Rabbit, associatedWithHours, 05:00–07:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHours Context triple: [Year of the Rabbit, associatedWithHours, 05:00–07:00]
-
A.
associatedWithTime
chosen
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
B.
associatedWithWorkforce
Indicates a relationship in which an entity is connected or related to a particular workforce, such as its members, activities, or management.
-
C.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
D.
associatedWithHorizon
Indicates a relationship in which something is linked or connected to a horizon, boundary, or limiting context.
-
E.
associatedWithCharge
Indicates a relationship where an entity is linked to, involved in, or connected with a specific charge or accusation.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cdce7081908ca1cf9107b87f61 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:02 p.m.