Triple
T705646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Meetinghouse |
E14092
|
entity |
| Predicate | targetCityDistrict |
P18717
|
FINISHED |
| Object | eastern Tokyo |
—
|
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: eastern Tokyo | Statement: [Operation Meetinghouse, targetCityDistrict, eastern Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCityDistrict Context triple: [Operation Meetinghouse, targetCityDistrict, eastern Tokyo]
-
A.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
B.
communityDistrictNumber
Indicates the specific community district identifier associated with an entity or location.
-
C.
majorDistrict
Indicates that one administrative district is the primary or most significant district associated with another entity or area.
-
D.
districtBasedOn
Indicates that one district is defined, derived, or established based on the boundaries, characteristics, or structure of another entity or area.
-
E.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
- F. None of above. chosen
Provenance (4 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4edc33881909a978268f6dd5d82 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a58c0a84819094f07658dc651b36 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:36 p.m.