Triple
T26502673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mile Rock Beach |
E669460
|
entity |
| Predicate | closestNeighborhood |
P62844
|
FINISHED |
| Object | Outer Richmond |
—
|
NE NERFINISHED |
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: Outer Richmond | Statement: [Mile Rock Beach, closestNeighborhood, Outer Richmond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestNeighborhood Context triple: [Mile Rock Beach, closestNeighborhood, Outer Richmond]
-
A.
closestTo
Indicates that one entity is nearer in distance to a reference entity than any other comparable entity.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
nearestPass
Indicates that one entity is the closest in distance or proximity to another entity compared to all other possible entities or paths.
-
D.
nearestArea
chosen
Indicates that one area is the closest in distance to a given reference point or region compared to all other candidate areas.
-
E.
nearestNeighborGroup
Indicates that one entity belongs to a group defined by being the closest or most immediately adjacent neighbors to another entity according to some distance or similarity measure.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 1:14 a.m.