Triple
T25980442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory Heights |
E646053
|
entity |
| Predicate | transportationAccessTo |
P69365
|
FINISHED |
| Object | Seattle, Washington |
—
|
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: Seattle, Washington | Statement: [Gregory Heights, transportationAccessTo, Seattle, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationAccessTo Context triple: [Gregory Heights, transportationAccessTo, Seattle, Washington]
-
A.
transportAccessType
Indicates the type or mode of transportation access available or used in a given context.
-
B.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
C.
transportAccessFrom
Indicates that one location or entity has transportation access originating from another specified location or source.
-
D.
transportationAccessPlan
Indicates that there is a planned or defined arrangement for how transportation services or infrastructure will be accessed or used.
-
E.
hasTransitAccessTo
chosen
Indicates that one place or entity is reachable from another via public or shared transportation services.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 22, 2026, 8:54 a.m.