Triple
T29511037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bantan Line |
E748651
|
entity |
| Predicate | ownerBefore |
P165080
|
FINISHED |
| Object | Japanese National Railways |
—
|
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: Japanese National Railways | Statement: [Bantan Line, ownerBefore, Japanese National Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerBefore Context triple: [Bantan Line, ownerBefore, Japanese National Railways]
-
A.
ownerBeforeJNR
chosen
Indicates that one entity was the owner of another entity prior to a specific reference point or event (e.g., before a junior or subsequent ownership change).
-
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.
ownershipSince
Indicates the point in time from which an entity has continuously owned another entity.
-
D.
primaryOwner
Indicates that one entity is the main or principal owner of another entity, having the highest level of ownership or control among all possible owners.
-
E.
ownershipStart
Indicates the point in time at which an entity begins to own or hold legal possession 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 4:32 p.m.