Triple
T20034054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephemeris Time |
E497211
|
entity |
| Predicate | formalDefinitionYear |
P131810
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Ephemeris Time, formalDefinitionYear, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalDefinitionYear Context triple: [Ephemeris Time, formalDefinitionYear, 1952]
-
A.
mathematicalFormalizationYear
Indicates the year in which something was first formally defined or expressed in mathematical terms.
-
B.
definedInYear
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
-
C.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
-
D.
yearFormalized
chosen
Indicates the specific year in which the relationship, concept, or entity was officially established, recognized, or formalized.
-
E.
redefinitionYear
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662e6a7e481908069c1de2b3f94e0 |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:36 p.m.