Triple
T28879096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊良部大橋 |
E732362
|
entity |
| Predicate | 料金徴収 |
P109497
|
FINISHED |
| Object | なし |
—
|
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: なし | Statement: [伊良部大橋, 料金徴収, なし]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 料金徴収 Context triple: [伊良部大橋, 料金徴収, なし]
-
A.
chargesFeeFor
chosen
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
B.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
C.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
D.
fieldCharge
Indicates a relationship where an entity is assigned, responsible for, or associated with a particular field-related duty, task, or area of oversight.
-
E.
legalCharge
Indicates that an authority has formally accused an entity of committing a specific legal offense or violation.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4d874c819094de2d585e1f5816 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:41 a.m.