Triple
T21685012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 長門国豊浦郡下関 |
E535206
|
entity |
| Predicate | 関連史料区分 |
P127424
|
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.
historicalMaterial
Indicates that something serves as a source or document providing information or evidence about past events or conditions.
-
B.
historicalResource
Indicates that a resource has historical significance or relevance, typically documenting or representing past events, conditions, or contexts.
-
C.
relatedClassification
chosen
Indicates a relationship where one classification is associated with, linked to, or otherwise contextually connected to another classification.
-
D.
historicalIdentificationOf
Indicates that one entity has been identified, classified, or recognized as another entity within a historical context or by historical sources.
-
E.
historicalClassificationEnd
Indicates the point in time when a particular historical classification or categorization of an entity ceases to be valid.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ca668481909f53853c7a8ea811 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.