Triple
T16984377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biwa-ko Line |
E412024
|
entity |
| Predicate | isSectionNameOf |
P82192
|
FINISHED |
| Object | Tōkaidō Main Line between Kyoto and Maibara |
—
|
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: Tōkaidō Main Line between Kyoto and Maibara | Statement: [Biwa-ko Line, isSectionNameOf, Tōkaidō Main Line between Kyoto and Maibara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSectionNameOf Context triple: [Biwa-ko Line, isSectionNameOf, Tōkaidō Main Line between Kyoto and Maibara]
-
A.
isNamedSectionOf
chosen
Indicates that one entity is a specifically named section or subdivision that forms part of another entity.
-
B.
isOnSectionOf
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
C.
isSectionNumber
Indicates that one entity is the section number identifier associated with another entity, typically within a structured document or text.
-
D.
hasSectionIn
Indicates that one entity contains or includes another entity as a section or subdivision within it.
-
E.
hasSectionNickname
Indicates that an entity (such as a section or subdivision) is known or referred to by a particular nickname.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18a0bf881908c449f499eb86495 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.