Triple
T37061223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 芥川 |
E917328
|
entity |
| Predicate | 関連文化財 |
P122266
|
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.
culturalProperty
chosen
Indicates that something is recognized or treated as a cultural property, typically denoting legal or heritage status tied to cultural significance.
-
B.
relationshipToNationalTreasures
Indicates a specified type of connection or association that an entity has with designated national treasures.
-
C.
関連城郭
Indicates a relationship where something is associated with or related to a particular castle or fortification.
-
D.
hasCulturalHeritageLink
Indicates a relationship where one entity is culturally derived from, influenced by, or historically connected to another.
-
E.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.