Triple
T27455894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōme Line |
E692590
|
entity |
| Predicate | hasStationAreaCharacteristic |
P6822
|
FINISHED |
| Object | residential suburbs |
—
|
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: residential suburbs | Statement: [Ōme Line, hasStationAreaCharacteristic, residential suburbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationAreaCharacteristic Context triple: [Ōme Line, hasStationAreaCharacteristic, residential suburbs]
-
A.
hasCatchmentAreaCharacteristic
Indicates that a catchment area possesses a specified characteristic, feature, or property.
-
B.
hasStationDistrict
Indicates that a station is located within or associated with a particular administrative district.
-
C.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
D.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
E.
coreAreaCharacteristic
Indicates that a characteristic or feature is specifically associated with the core area of something, rather than its peripheral or secondary parts.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 12:48 p.m.