Triple
T4190060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Tobacco Village, Maryland |
E89011
|
entity |
| Predicate | distanceToLaPlata |
P54563
|
FINISHED |
| Object | approximately 2 miles west |
—
|
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 2 miles west | Statement: [Port Tobacco Village, Maryland, distanceToLaPlata, approximately 2 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLaPlata Context triple: [Port Tobacco Village, Maryland, distanceToLaPlata, approximately 2 miles west]
-
A.
distanceFromBuenosAires
Indicates the measured distance between a given entity’s location and the city of Buenos Aires.
-
B.
distanceFromPotosiApproximate
Indicates an approximate measure of how far something is from Potosi.
-
C.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
-
D.
distanceToSantiago_km
Indicates the physical distance, measured in kilometers, between a given location and Santiago.
-
E.
distanceToSouthAmerica
Indicates the spatial distance between a given entity’s location and the continent of South America.
- F. None of above. chosen
Provenance (4 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af04af4e44819098a9d7f91e65adf2 |
completed | March 9, 2026, 5:34 p.m. |
Created at: March 9, 2026, 3:46 p.m.