Triple
T27457703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsurumi Line |
E692645
|
entity |
| Predicate | ownerBeforeJNR |
P165080
|
FINISHED |
| Object | private industrial railway company |
—
|
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: private industrial railway company | Statement: [Tsurumi Line, ownerBeforeJNR, private industrial railway company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerBeforeJNR Context triple: [Tsurumi Line, ownerBeforeJNR, private industrial railway company]
-
A.
ownerBeforeJNRBreakup
Indicates that one entity was the owner of another entity prior to the breakup of the Japanese National Railways (JNR).
-
B.
ownerLater
Indicates that one entity becomes the owner of another entity at a later point in time, after some prior state or ownership.
-
C.
previousMaintainer
Indicates that one entity formerly held responsibility for maintaining another entity before the current maintainer.
-
D.
ownerAfterRebranding
Indicates that an entity is the owner of another entity specifically after a rebranding event has taken place.
-
E.
previousMajorOwner
Indicates that one entity was the most recent significant owner of another entity before the current owner.
- F. None of above. chosen
Provenance (4 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_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 12:49 p.m.