Triple
T19831164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC |
E476463
|
entity |
| Predicate | laterEpochUsedInRevisions |
P21934
|
FINISHED |
| Object | J2000.0 |
—
|
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.0 | Statement: [NGC, laterEpochUsedInRevisions, J2000.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEpochUsedInRevisions Context triple: [NGC, laterEpochUsedInRevisions, J2000.0]
-
A.
laterAgeRevision
Indicates that one entity represents a revised age that is later (or updated to a more advanced point in time) than the age specified by another entity.
-
B.
previousVersionInUseUntil
Indicates that an earlier version of something continued to be actively used up to a specified point in time.
-
C.
epochReference
chosen
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
D.
earliestEpochOf
Indicates the earliest time point or epoch at which a given entity, event, or state first occurs or becomes valid in relation to another.
-
E.
periodicallyRevisedAt
Indicates that something is updated or revised at recurring, regular points 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.