Triple
T80112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Electrodynamics of Moving Bodies |
E1608
|
entity |
| Predicate | datePublished |
P25
|
FINISHED |
| Object | 30 June 1905 |
—
|
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: 30 June 1905 | Statement: [On the Electrodynamics of Moving Bodies, datePublished, 30 June 1905]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePublished Context triple: [On the Electrodynamics of Moving Bodies, datePublished, 30 June 1905]
-
A.
publicationYear
chosen
Indicates the specific calendar year in which a work was formally published or released.
-
B.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
C.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
D.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
E.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eb126b48190b410b859c1be99aa |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.