Triple
T11742593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR West 321 series EMU |
E279191
|
entity |
| Predicate | serviceFrequencyRole |
P61818
|
FINISHED |
| Object | used on high-frequency timetables |
—
|
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: used on high-frequency timetables | Statement: [JR West 321 series EMU, serviceFrequencyRole, used on high-frequency timetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceFrequencyRole Context triple: [JR West 321 series EMU, serviceFrequencyRole, used on high-frequency timetables]
-
A.
serviceFrequencyContext
chosen
Indicates the contextual conditions or circumstances under which a service’s frequency is defined, applied, or interpreted.
-
B.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
C.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
D.
measurementFrequency
Indicates how often a measurement is taken or recorded over time.
-
E.
inspectionFrequency
Indicates how often an entity is examined, checked, or reviewed within a given time period.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f191388190bd6ef7e80c41ca48 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.