Triple
T35560951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAT |
E1027633
|
entity |
| Predicate | localizationAccuracy_arcmin |
P124081
|
FINISHED |
| Object | 1–4 |
—
|
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: 1–4 | Statement: [BAT, localizationAccuracy_arcmin, 1–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localizationAccuracy_arcmin Context triple: [BAT, localizationAccuracy_arcmin, 1–4]
-
A.
typicalHorizontalAccuracy
Indicates the usual or expected degree of precision in the horizontal (x–y) position of a measurement or location estimate.
-
B.
azimuthAccuracy
Indicates the degree of precision or allowable error in the measured or specified azimuth angle between entities.
-
C.
astrometricAccuracy
chosen
Indicates the degree of precision with which the position and motion of an astronomical object are measured or determined.
-
D.
minimumGeoTargetingAccuracy
Indicates the lowest acceptable level of geographic precision required when targeting locations for an action or relationship.
-
E.
elevationAccuracy
Indicates the degree of precision or reliability associated with a measured or reported elevation value in the relationship.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:04 p.m.