Triple
T29508374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higashi Ward Office |
E748578
|
entity |
| Predicate | hasPublicContactType |
P41776
|
FINISHED |
| Object | in-person counter services |
—
|
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: in-person counter services | Statement: [Higashi Ward Office, hasPublicContactType, in-person counter services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicContactType Context triple: [Higashi Ward Office, hasPublicContactType, in-person counter services]
-
A.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
-
B.
hasContactMethod
chosen
Indicates that an entity has a specific way or channel through which it can be contacted.
-
C.
hasContactVariety
Indicates that one entity is associated with a specific type or variety of contact information or communication channel.
-
D.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
-
E.
hasContactState
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 4:29 p.m.