Triple
T20814625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR-P17 |
E512403
|
entity |
| Predicate | isTerminusCodeForLine |
P46766
|
FINISHED |
| Object | Sakurajima Line |
—
|
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: Sakurajima Line | Statement: [JR-P17, isTerminusCodeForLine, Sakurajima Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTerminusCodeForLine Context triple: [JR-P17, isTerminusCodeForLine, Sakurajima Line]
-
A.
isTerminal
Indicates that an entity represents an endpoint or final state in a process, structure, or sequence, with no further continuation beyond it.
-
B.
lineTerminusFor
chosen
Indicates that one entity serves as an endpoint or terminus of a particular line or linear feature represented by another entity.
-
C.
lineTerminusForSomeServices
Indicates that a location serves as the endpoint or terminus for at least some, but not necessarily all, of the services operating on a given line.
-
D.
isTerminalIn
Indicates that one entity functions as a terminal (end point or final element) within another entity, such as a structure, sequence, or process.
-
E.
definesLineTerminator
Indicates that one entity specifies what character or sequence of characters marks the end of a line for 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d4e43c8190aecce82a3f7e2de0 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.