Triple
T17759800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanyo Main Line |
E443338
|
entity |
| Predicate | gaugeCompatibleWith |
P128239
|
FINISHED |
| Object | most conventional lines in Japan |
—
|
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: most conventional lines in Japan | Statement: [Sanyo Main Line, gaugeCompatibleWith, most conventional lines in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaugeCompatibleWith Context triple: [Sanyo Main Line, gaugeCompatibleWith, most conventional lines in Japan]
-
A.
gaugeType
Indicates the specific kind or category of gauge associated with an entity or measurement.
-
B.
gaugeGroup
Indicates a relationship where a physical or theoretical model is associated with the gauge group that defines its underlying symmetry structure.
-
C.
gaugeRelationship
Indicates a relationship where one entity measures, assesses, or evaluates the state, quality, or degree of another entity.
-
D.
gaugeServed
Indicates that a gauge or measuring device is currently being supplied or serviced by a particular source or system.
-
E.
gaugeClass
Indicates that one entity is classified as a particular type or category of gauge.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48421c3048190b26864b72aad0d70 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3cfab7edc8190b663282d565a0389 |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:10 a.m.