Triple
T27423790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn Park, Maryland |
E690420
|
entity |
| Predicate | distanceToBaltimoreDowntownInMiles |
P33616
|
FINISHED |
| Object | approximately 5 |
—
|
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 5 | Statement: [Brooklyn Park, Maryland, distanceToBaltimoreDowntownInMiles, approximately 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBaltimoreDowntownInMiles Context triple: [Brooklyn Park, Maryland, distanceToBaltimoreDowntownInMiles, approximately 5]
-
A.
distanceToBaltimoreInMiles
chosen
Indicates the numerical distance, measured in miles, between a given location and the city of Baltimore.
-
B.
distanceFromBaltimorePennStation
Indicates the measured distance between a given location and Baltimore Penn Station.
-
C.
distanceToAnnapolisMiles
Indicates the physical distance, measured in miles, between a given location and Annapolis.
-
D.
distanceToAnnapolisInMilesApprox
Indicates the approximate distance, measured in miles, between a given entity and Annapolis.
-
E.
distanceToChesapeakeBay
Indicates the measured or estimated spatial distance between a given location and Chesapeake Bay.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: April 27, 2026, 12:40 p.m.