Triple
T33397262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barycentric Celestial Reference System |
E855203
|
entity |
| Predicate | relatedSystemAbbreviation |
P133893
|
FINISHED |
| Object | GCRS |
E1409107
|
NE 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: GCRS | Statement: [Barycentric Celestial Reference System, relatedSystemAbbreviation, GCRS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedSystemAbbreviation Context triple: [Barycentric Celestial Reference System, relatedSystemAbbreviation, GCRS]
-
A.
relatedAbbreviationSystem
chosen
Indicates that one entity is associated with, or belongs to, a particular system of abbreviations used to represent it.
-
B.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
C.
relatedApplication
Indicates that one application has a defined connection or association with another application, such as dependency, complementarity, or functional linkage.
-
D.
relatedOrganizationAbbreviation
Indicates that one organization is associated with another through a specific abbreviated form of its name or title.
-
E.
relatedRegistry
Indicates that one registry has an association or linkage to another registry.
- F. None of above.
Provenance (4 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3576f3e66c8190995d54139cd62438 |
completed | June 19, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:35 a.m.