Triple
T38672990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Grant Grove |
E943650
|
entity |
| Predicate | hasPavedPaths |
P141314
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [General Grant Grove, hasPavedPaths, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPavedPaths Context triple: [General Grant Grove, hasPavedPaths, yes]
-
A.
hasPavements
Indicates that a location or route is equipped with pavements (sidewalks) alongside it.
-
B.
hasPavementStatus
chosen
Indicates the type or condition of pavement associated with an entity, such as whether a surface is paved, unpaved, or its current pavement state.
-
C.
isPavedMostOfWay
Indicates that a route or path is surfaced with pavement for the majority of its length, though not necessarily entirely.
-
D.
pavedBy
Indicates that a surface, route, or area has been covered or constructed with a hard material by a specified agent or process.
-
E.
hasPermanentRoads
Indicates that an entity possesses roads that are constructed to be durable and remain in place over an extended period, rather than being temporary or seasonal.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: May 3, 2026, 4:33 p.m.