Triple
T33397256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barycentric Celestial Reference System |
E855203
|
entity |
| Predicate | timeCoordinateAbbreviation |
P15341
|
FINISHED |
| Object | TCB |
—
|
NE NERFINISHED |
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: TCB | Statement: [Barycentric Celestial Reference System, timeCoordinateAbbreviation, TCB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeCoordinateAbbreviation Context triple: [Barycentric Celestial Reference System, timeCoordinateAbbreviation, TCB]
-
A.
timeCoordinate
Indicates a relationship where a specific time value is used to locate or reference an event, state, or object along a temporal axis or timeline.
-
B.
timeCoordinateType
chosen
Indicates the specific temporal reference system or framework used to define and interpret time coordinates for an event or entity.
-
C.
historicalTimeAbbreviation
Indicates a shortened or abbreviated form used to represent a specific historical time period or era.
-
D.
timeNotation
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
E.
zoneAbbreviation
Indicates that one entity is the abbreviated or short-form representation of a particular zone associated with another entity.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.