Triple
T15248123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 品川区 |
E364438
|
entity |
| Predicate | establishedAsWard |
P5762
|
FINISHED |
| Object | 1947年3月15日 |
—
|
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: 1947年3月15日 | Statement: [品川区, establishedAsWard, 1947年3月15日]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsWard Context triple: [品川区, establishedAsWard, 1947年3月15日]
-
A.
isWardOf
Indicates that one entity is under the guardianship, protection, or legal care of another entity as their ward.
-
B.
establishedAs
chosen
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
C.
containsWard
Indicates that one entity includes, encompasses, or has within it a ward (such as a district, division, or dependent person) as part of its scope or responsibility.
-
D.
electoralWardFor
Indicates that one entity serves as the electoral ward or voting district in which another entity (such as a place or address) is located or represented.
-
E.
locatedInCityWard
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f4f9d48190b96a7e0c6993cd69 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.