Triple
T10319541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Terrestrial Reference System |
E242103
|
entity |
| Predicate | accuracyGoal |
P31957
|
FINISHED |
| Object | millimeter-level stability |
—
|
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: millimeter-level stability | Statement: [International Terrestrial Reference System, accuracyGoal, millimeter-level stability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accuracyGoal Context triple: [International Terrestrial Reference System, accuracyGoal, millimeter-level stability]
-
A.
landingPrecisionGoal
Indicates the intended level of accuracy or closeness with which a landing is planned to reach its target location.
-
B.
accuracyDependsOn
Indicates that the accuracy of one entity or process is contingent upon, or influenced by, another entity or factor.
-
C.
goalNumber
Indicates that an entity is associated with a specific target or objective quantified as a number.
-
D.
hasAccuracy
Indicates that something possesses a specified level or measure of correctness, precision, or exactness in relation to a standard or reference.
-
E.
stabilityGoal
chosen
Indicates a relationship where an action, policy, or entity is aimed at achieving, maintaining, or enhancing stability in a given system or context.
- 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.