Triple
T9893736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hikone Castle |
E181517
|
entity |
| Predicate | hasMainKeepType |
P91023
|
FINISHED |
| Object | tenshu |
—
|
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: tenshu | Statement: [Hikone Castle, hasMainKeepType, tenshu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainKeepType Context triple: [Hikone Castle, hasMainKeepType, tenshu]
-
A.
hasMainArch
Indicates that an entity possesses or features a primary or central arch structure.
-
B.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
C.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
D.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
E.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb48271d48190b718c7f6b2fe315b |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:39 p.m.