Triple
T32977057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inuyama Castle |
E843692
|
entity |
| Predicate | nationalTreasureSince |
P192233
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Inuyama Castle, nationalTreasureSince, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalTreasureSince Context triple: [Inuyama Castle, nationalTreasureSince, 1952]
-
A.
nationalTreasureNumber
Indicates that an entity is assigned a specific official national treasure identification number within a country’s heritage or cultural registry.
-
B.
designatedAsNationalTreasureBy
Indicates that an entity has been officially recognized and declared a national treasure by a specific authority or country.
-
C.
nationalMuseum
Indicates that an entity functions as a primary, officially recognized museum representing a nation at the national level.
-
D.
nationalMonument
Indicates that something has been officially designated as a national monument by a country or governing authority.
-
E.
treasuryKnownFor
Indicates that a treasury is recognized or notable for a particular characteristic, function, asset, or achievement.
- F. None of above. chosen
Provenance (4 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.