Triple
T3867975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday |
E91907
|
entity |
| Predicate | ISO8601Position |
P12859
|
FINISHED |
| Object | day 7 |
—
|
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: day 7 | Statement: [Sunday, ISO8601Position, day 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO8601Position Context triple: [Sunday, ISO8601Position, day 7]
-
A.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
B.
representedInISO8601
chosen
Indicates that a temporal value or duration is expressed using the ISO 8601 standardized date and time format.
-
C.
positionInCivilYear
Indicates the specific point or ordering of something within the sequence of time units that make up a civil (calendar) year.
-
D.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
E.
relativePositionToInternationalDateLine
Indicates the spatial relationship of an entity’s location with respect to the International Date Line (e.g., whether and how it lies to the east, west, or across it).
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3cc1a88190924125a86f72fd5b |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.