Triple
T35447022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 土佐国高知 |
E1024514
|
entity |
| Predicate | importantEra |
P561
|
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: [土佐国高知, importantEra, 幕末]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantEra Context triple: [土佐国高知, importantEra, 幕末]
-
A.
hasEraSignificance
Indicates that something holds notable importance, influence, or relevance within a particular historical era or time period.
-
B.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
C.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
D.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
E.
bearerNotableEra
Indicates that a bearer (such as a title, role, or office) is notably associated with a particular historical era or time period.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.