Triple
T16690855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HRSC |
E405588
|
entity |
| Predicate | verticalAccuracy |
P31701
|
FINISHED |
| Object | on the order of a few meters |
—
|
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: on the order of a few meters | Statement: [HRSC, verticalAccuracy, on the order of a few meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verticalAccuracy Context triple: [HRSC, verticalAccuracy, on the order of a few meters]
-
A.
typicalHorizontalAccuracy
Indicates the usual or expected degree of precision in the horizontal (x–y) position of a measurement or location estimate.
-
B.
elevationAccuracy
chosen
Indicates the degree of precision or reliability associated with a measured or reported elevation value in the relationship.
-
C.
azimuthAccuracy
Indicates the degree of precision or allowable error in the measured or specified azimuth angle between entities.
-
D.
hasAccuracy
Indicates that something possesses a specified level or measure of correctness, precision, or exactness in relation to a standard or reference.
-
E.
verticalLocation
Indicates a vertical positional relationship where one entity is located above or below another along the up-down axis.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea8cabc8190ba321503399960da |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.