Triple
T27392709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanoya |
E691580
|
entity |
| Predicate | drivingLicenseAuthority |
P108937
|
FINISHED |
| Object | Japan |
—
|
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: Japan | Statement: [Kanoya, drivingLicenseAuthority, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingLicenseAuthority Context triple: [Kanoya, drivingLicenseAuthority, Japan]
-
A.
licenceAuthority
chosen
Indicates that one entity has the official power or jurisdiction to grant, issue, or regulate licences for another entity or activity.
-
B.
vehicleRegistrationAuthority
Indicates the authority or organization responsible for officially registering a vehicle and maintaining its registration records.
-
C.
countryOfLicence
Indicates the country that has issued or granted a particular licence.
-
D.
cityOfLicense
Indicates the city in which an entity (typically a broadcast station or similar regulated service) is officially licensed or authorized to operate.
-
E.
fccLicensingAuthority
Indicates that an entity serves as the licensing authority recognized or regulated by the U.S. Federal Communications Commission (FCC) for another entity or regulated item.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:26 p.m.