Triple
T22440417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伏見櫓 |
E554738
|
entity |
| Predicate | 位置的特徴 |
P46334
|
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.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
-
B.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
C.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
D.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
E.
positionDescribed
Indicates that a position, location, or spatial arrangement of an entity is explicitly specified or characterized, typically in descriptive terms.
- 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_69f15ae1f82881908a611f134eb03f3d |
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.