Triple
T37440683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōkuma-machi |
E930410
|
entity |
| Predicate | partiallyReopenedForResidents |
P30722
|
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: [Ōkuma-machi, partiallyReopenedForResidents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyReopenedForResidents Context triple: [Ōkuma-machi, partiallyReopenedForResidents, true]
-
A.
reopenedPartially
chosen
Indicates that an entity that was previously closed or inactive has been opened again, but only to a limited or incomplete extent.
-
B.
partiallyClosed
Indicates that something is not fully closed, but also not fully open, occupying an intermediate state of closure.
-
C.
partialReopeningDate
Indicates the date on which an entity is reopened in a limited or partial capacity, rather than fully resuming normal operation.
-
D.
fullyReopened
Indicates that something previously closed or partially open has been restored to complete, unrestricted operational status.
-
E.
reopeningToPublic
Indicates that an entity, previously closed or restricted, is being opened again for access or use by the general public.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:17 p.m.