Triple
T30307196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Date clan |
E770817
|
entity |
| Predicate | baseCastle |
P22469
|
FINISHED |
| Object | Yonezawa Castle |
—
|
NE NERFINISHED |
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: Yonezawa Castle | Statement: [Date clan, baseCastle, Yonezawa Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseCastle Context triple: [Date clan, baseCastle, Yonezawa Castle]
-
A.
castle
Indicates that one entity is a castle associated with, located at, or serving as the stronghold or residence for another entity.
-
B.
hasCastle
chosen
Indicates that one entity possesses, controls, or contains a castle.
-
C.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
-
D.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
E.
castlePosition
Indicates the spatial location or placement of a castle relative to a reference point or area.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816966e8819094d81abb060be372 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:49 p.m.