Triple
T37060643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 四條畷市 |
E917313
|
entity |
| Predicate | 史跡 |
P81077
|
FINISHED |
| Object | 飯盛城跡 |
—
|
NE NERFINISHED |
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.
遺構
Indicates the existence or presence of physical remains, ruins, or structural traces left from past constructions, activities, or settlements.
-
B.
歴史
Indicates a relationship where something pertains to, records, or is involved in the events, development, or study of the past over time.
-
C.
otherHistoricSee
chosen
Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
-
D.
再建の歴史
Indicates a historical relationship of repeated reconstruction or rebuilding events associated with an entity over time.
-
E.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
- 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.