Triple
T35339584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Honda, California |
E1020559
|
entity |
| Predicate | nearestInlandCity |
P183039
|
FINISHED |
| Object | Redwood City, California |
—
|
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: Redwood City, California | Statement: [La Honda, California, nearestInlandCity, Redwood City, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestInlandCity Context triple: [La Honda, California, nearestInlandCity, Redwood City, California]
-
A.
nearestCityTo
Indicates that one city is the closest in distance to a given location or entity compared to all other cities.
-
B.
nearestCoastalCity
Indicates that one city is the closest coastal city to another location or city, based on geographic distance.
-
C.
nearestIslandCity
Indicates that one city is the closest city located on an island relative to a given reference location or city.
-
D.
nearestCoastalTown
Indicates that one town is the closest coastal town geographically relative to a given reference location or town.
-
E.
nearestCitySouth
Indicates that one city is the closest city located to the south of another city.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.