Triple
T13179781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AllWISE Source Catalog |
E313691
|
entity |
| Predicate | coordinateEpoch |
P66369
|
FINISHED |
| Object | J2000 |
—
|
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: J2000 | Statement: [AllWISE Source Catalog, coordinateEpoch, J2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateEpoch Context triple: [AllWISE Source Catalog, coordinateEpoch, J2000]
-
A.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
B.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
C.
equatorialCoordinateEpoch
chosen
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
D.
timeCoordinateType
Indicates the specific temporal reference system or framework used to define and interpret time coordinates for an event or entity.
-
E.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.