Triple
T28944322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adachi City Government |
E730537
|
entity |
| Predicate | offersServicesIn |
P81416
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Adachi City Government, offersServicesIn, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersServicesIn Context triple: [Adachi City Government, offersServicesIn, Japanese]
-
A.
offersServiceIn
chosen
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
B.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
-
C.
offersServiceOn
Indicates that one entity provides or makes a service available on, during, or through another entity (such as a platform, date, or location).
-
D.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
E.
offeredService
Indicates that one entity has provided or made available a service to another entity.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 8:39 a.m.