Triple
T27455886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōme Line |
E692590
|
entity |
| Predicate | railwayCompanyAfterJNRPrivatization |
P55892
|
FINISHED |
| Object | JR East |
—
|
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: JR East | Statement: [Ōme Line, railwayCompanyAfterJNRPrivatization, JR East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayCompanyAfterJNRPrivatization Context triple: [Ōme Line, railwayCompanyAfterJNRPrivatization, JR East]
-
A.
laterRailwayCompany
chosen
Indicates that one railway company is the successor or later incarnation of another railway company.
-
B.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
C.
railwayCompanyType
Indicates the specific category or classification of a railway company in terms of its role, ownership, or operational type.
-
D.
railwayCompanyTestedOn
Indicates that a railway company has been subjected to a test, evaluation, or assessment in relation to a specified entity or context.
-
E.
railwayCompanyGroup
Indicates that one entity is a group or consortium that includes or controls the other entity as a railway company.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 12:48 p.m.