Triple
T26551417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 福岡県太宰府市 |
E671686
|
entity |
| Predicate | 有名な史跡 |
P18735
|
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.
notableArchaeologicalSite
chosen
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
B.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
C.
bestKnownAsSiteOf
Indicates that a place is most widely recognized or famous for being the location where a particular event, activity, or feature occurs or is found.
-
D.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
E.
heritageSiteName
Indicates the official or commonly recognized name assigned to a heritage 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f614624c80819084f6febf57f86828 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:47 a.m.