Triple
T23277887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Street subway station |
E588772
|
entity |
| Predicate | accessibleByMode |
P119199
|
FINISHED |
| Object | walking |
—
|
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: walking | Statement: [Arlington Street subway station, accessibleByMode, walking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibleByMode Context triple: [Arlington Street subway station, accessibleByMode, walking]
-
A.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
B.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
availableInMode
chosen
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
E.
accessibleWithin
Indicates that one entity can be reached, used, or entered from within the spatial or contextual bounds of another entity.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957991108190ac82fa6dd355f722 |
completed | April 29, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:49 p.m.