Triple
T20034124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barycentric Dynamical Time |
E497212
|
entity |
| Predicate | definedOnGeoid |
P4464
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Barycentric Dynamical Time, definedOnGeoid, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedOnGeoid Context triple: [Barycentric Dynamical Time, definedOnGeoid, no]
-
A.
definedOn
chosen
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
B.
geographicallyDefinedAs
Indicates that one entity’s geographic extent, boundaries, or location is defined or characterized in terms of another geographic entity.
-
C.
hasGeodeticPurpose
Indicates that something is associated with or serves a specific geodetic purpose, such as measurement, reference, or positioning in geodesy.
-
D.
hasGeographicBasis
Indicates that something is grounded in, derived from, or defined by a particular geographic location or area.
-
E.
geographicalRepresentation
Indicates that one entity serves as a geographic depiction, model, or mapping of another entity’s location, area, or spatial characteristics.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662e6a7e481908069c1de2b3f94e0 |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:36 p.m.