Triple
T32583611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akashi Castle |
E832856
|
entity |
| Predicate | hasDonjon |
P100053
|
FINISHED |
| Object | no surviving main keep |
—
|
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: no surviving main keep | Statement: [Akashi Castle, hasDonjon, no surviving main keep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDonjon Context triple: [Akashi Castle, hasDonjon, no surviving main keep]
-
A.
notableDungeon
Indicates that an entity is recognized as a significant or noteworthy dungeon, typically due to its importance, uniqueness, or prominence.
-
B.
hasDungeon
chosen
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
C.
hasFictionalCastle
Indicates that an entity possesses or is associated with a castle that exists only in fiction or imaginative works, not in reality.
-
D.
GothicCommander
Indicates a relationship where an entity holds the role or title of a commander within a Gothic context, such as a Gothic army, faction, or cultural group.
-
E.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:04 a.m.