Triple
T35158277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doshisha schools |
E1015187
|
entity |
| Predicate | notableCampusLocation |
P13186
|
FINISHED |
| Object | Imadegawa, Kyoto |
E1167240
|
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: Imadegawa, Kyoto | Statement: [Doshisha schools, notableCampusLocation, Imadegawa, Kyoto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCampusLocation Context triple: [Doshisha schools, notableCampusLocation, Imadegawa, Kyoto]
-
A.
notableCampusArea
Indicates that a campus area is particularly significant, prominent, or well-known within the context of the institution.
-
B.
campusLandmark
chosen
Indicates that something serves as a notable or recognizable landmark located on or associated with a campus.
-
C.
positionOnCampus
Indicates the spatial location or placement of an entity within the boundaries or layout of a campus.
-
D.
notableInstitution
Indicates that an institution holds particular significance, prominence, or recognition in relation to the subject.
-
E.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
- 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_69f76ddb3a708190b521ba2970b17178 |
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_6a3803fa65c0819092f953a1bc47514c |
completed | June 21, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.