Triple
T10319597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Celestial Reference System |
E242104
|
entity |
| Predicate | frameOrigin |
P82918
|
FINISHED |
| Object | solar system barycenter |
—
|
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: solar system barycenter | Statement: [International Celestial Reference System, frameOrigin, solar system barycenter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameOrigin Context triple: [International Celestial Reference System, frameOrigin, solar system barycenter]
-
A.
frame
Indicates placing or presenting something within a particular context, structure, or perspective that shapes how it is interpreted.
-
B.
frameLocation
chosen
Indicates that one entity serves as the spatial or contextual frame of reference within which another entity is located or interpreted.
-
C.
frameWidth
Indicates the measurement of how wide a frame is, typically specifying its horizontal extent or thickness.
-
D.
frameType
Indicates the specific structural or categorical kind of frame associated with an entity or relation.
-
E.
framedBy
Indicates that one entity serves as a surrounding boundary or enclosing structure that visually or conceptually frames 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.