Triple
T33329554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 仁徳天皇 |
E853363
|
entity |
| Predicate | 関連伝承地 |
P79177
|
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.
heritageSiteAssociatedWith
chosen
Indicates a relationship where a heritage site is connected or linked to another entity, such as a person, event, culture, or location, through historical, cultural, or symbolic association.
-
B.
関連城郭
Indicates a relationship where something is associated with or related to a particular castle or fortification.
-
C.
associatedShrineComplex
Indicates that one entity is linked or connected to a particular shrine complex, typically through location, function, or religious association.
-
D.
associatedShrine
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.