Triple
T37757406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usui Pass section between Yokokawa and Karuizawa |
E941153
|
entity |
| Predicate | requiredBankEngines |
P202621
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Usui Pass section between Yokokawa and Karuizawa, requiredBankEngines, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredBankEngines Context triple: [Usui Pass section between Yokokawa and Karuizawa, requiredBankEngines, true]
-
A.
usesBanking
Indicates that one entity makes use of the banking services, facilities, or systems provided by another entity.
-
B.
servesBank
Indicates that one entity provides banking or financial services to another entity.
-
C.
hasBanking
Indicates that one entity provides or is associated with banking services or facilities for another entity.
-
D.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
E.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00a15604fc8190b1c280794960f3a4 |
completed | May 10, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_6a00a0f7e77881909ac85755ab0e6329 |
completed | May 10, 2026, 3:15 p.m. |
| PDg | Predicate description generation | batch_6a00a154c3b0819088de3f22f3f81040 |
completed | May 10, 2026, 3:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.