Triple
T25006606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anansi |
E625855
|
entity |
| Predicate | dayNameAssociation |
P22641
|
FINISHED |
| Object | Wednesday |
—
|
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: Wednesday | Statement: [Anansi, dayNameAssociation, Wednesday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayNameAssociation Context triple: [Anansi, dayNameAssociation, Wednesday]
-
A.
dayName
chosen
Indicates the specific name of the day of the week associated with a given date or time.
-
B.
dayNamingBasis
Indicates the principle or reference (such as an event, object, or concept) on which the naming of a day is based.
-
C.
dayName7
Indicates that the relationship specifies the name of the seventh day of the week associated with a given day entity.
-
D.
nameDayPartAssociation
Indicates an association between a specific name and a particular part of the day (e.g., morning, afternoon, evening, night).
-
E.
dayName4
Indicates that an entity is associated with the name of the fourth day of the week (e.g., Thursday), expressing a mapping from a day to its conventional name.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b113f8c8190ae05102e9c2ae076 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.