Triple
T34991249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamanote district |
E1009389
|
entity |
| Predicate | includesHistorically |
P59380
|
FINISHED |
| Object | Yotsuya area |
E1709627
|
NE 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: Yotsuya area | Statement: [Yamanote district, includesHistorically, Yotsuya area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHistorically Context triple: [Yamanote district, includesHistorically, Yotsuya area]
-
A.
includesHistoricSee
Indicates that something contains or encompasses a historically significant site, feature, or point of interest.
-
B.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
C.
historicallyEncompassed
chosen
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
-
D.
includeHistoricalSee
Indicates that a relationship or reference should also encompass or display historically related "see also" connections or pointers.
-
E.
historicallyIndicates
Indicates that one entity serves as evidence, a sign, or a marker of another entity specifically within a historical context or time period.
- F. None of above.
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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3803ee73348190b377b15cf93ac660 |
completed | June 21, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.