Triple
T25130970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K_J |
E629520
|
entity |
| Predicate | hasExactValueSince |
P9774
|
FINISHED |
| Object | 2019-05-20 |
—
|
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: 2019-05-20 | Statement: [K_J, hasExactValueSince, 2019-05-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExactValueSince Context triple: [K_J, hasExactValueSince, 2019-05-20]
-
A.
isExactSince
Indicates that a condition, state, or relationship has held precisely from a specific starting time onward, with that start time being exact rather than approximate.
-
B.
hasExactValue
chosen
Indicates that an entity possesses a specific, precisely defined value that must match exactly, without any deviation or tolerance.
-
C.
hasClockSince
Indicates that an entity has possessed or maintained a clock continuously from a specified point in time onward.
-
D.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
E.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 6:28 a.m.