Triple
T38033959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohmi Railway (pre-war private railway) |
E948996
|
entity |
| Predicate | relatedToModernEntity |
P201639
|
FINISHED |
| Object | Ohmi Railway Co., Ltd. |
E1021349
|
NE 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: Ohmi Railway Co., Ltd. | Statement: [Ohmi Railway (pre-war private railway), relatedToModernEntity, Ohmi Railway Co., Ltd.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToModernEntity Context triple: [Ohmi Railway (pre-war private railway), relatedToModernEntity, Ohmi Railway Co., Ltd.]
-
A.
linkedToModernState
Indicates that an entity has a historical, legal, or conceptual connection to a present-day sovereign state.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
D.
associatedWithModernTown
Indicates that something has a defined connection or linkage to a present-day town or municipality.
-
E.
successorOrRelatedEntity
chosen
Indicates that one entity is a successor to, or otherwise closely related in lineage or function to, another entity.
- F. None of above.
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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d2ed3c481908c89a693606df4e5 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.