Triple
T25938131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRQZ |
E653616
|
entity |
| Predicate | outerZoneRadius |
P67815
|
FINISHED |
| Object | approximately 100 miles |
—
|
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: approximately 100 miles | Statement: [NRQZ, outerZoneRadius, approximately 100 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerZoneRadius Context triple: [NRQZ, outerZoneRadius, approximately 100 miles]
-
A.
outermostZone
Indicates that one entity is the outermost or furthest boundary zone enclosing or surrounding another entity or area.
-
B.
outerHaloRadius
Indicates the distance from the center of an object to the outer boundary of its surrounding halo or diffuse outer region.
-
C.
hasOuterBoundaryRadius
chosen
Indicates that an entity has an outer boundary characterized by a specific radius measurement.
-
D.
chargeRadius
Indicates the characteristic radial distance around an entity within which its electric charge or charge-related influence is considered effective.
-
E.
outerBoundary
Indicates that one entity serves as the enclosing outer limit or perimeter that bounds another entity or region.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6045b07b08190a58fd7e0acda574c |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:40 a.m.