Triple
T22440358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 吹上御苑 |
E554737
|
entity |
| Predicate | 位置関係 |
P23578
|
FINISHED |
| Object | 皇居の北西部に位置する |
—
|
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: 皇居の北西部に位置する | Statement: [吹上御苑, 位置関係, 皇居の北西部に位置する]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 位置関係 Context triple: [吹上御苑, 位置関係, 皇居の北西部に位置する]
-
A.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
B.
spatialRelation
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
-
C.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
meetsInRelationTo
Indicates that two or more entities come together or interact within the context of a specified relationship or circumstance.
-
E.
angleRelation
Indicates a relationship specifying how two or more angles are related to each other, such as being equal, complementary, supplementary, or otherwise geometrically constrained.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae0edcc8190919b198035de0df2 |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.