Triple
T14525748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 日本国旗 |
E340770
|
entity |
| Predicate | 歴史的起源 |
P1614
|
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.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
hasHistoricalOrigin
chosen
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
C.
historicalBackground
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
D.
historicalConceptEmergence
Indicates the point or process by which a historical concept first appears, develops, or becomes recognized within a particular temporal or cultural context.
-
E.
historicalFormation
Indicates the process or circumstances through which something came into existence or took shape over time in history.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea050781881909ed685d94479bf99 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.