Triple
T18860674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bottmingen |
E461302
|
entity |
| Predicate | Bottmingen Castle instanceOf |
P101962
|
FINISHED |
| Object | moated castle |
—
|
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: moated castle | Statement: [Bottmingen, Bottmingen Castle instanceOf, moated castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Bottmingen Castle instanceOf Context triple: [Bottmingen, Bottmingen Castle instanceOf, moated castle]
-
A.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
-
B.
hasFamousCastle
Indicates that an entity possesses or is the location of a castle that is widely recognized or renowned.
-
C.
Bytča Castle_instanceOf
Indicates that the entity Bytča Castle is an instance or specific example of a more general class or type.
-
D.
largestInhabitedCastleIn
Indicates that a castle is the largest inhabited castle located within a given geographic area or region.
-
E.
castle
chosen
Indicates that one entity is a castle associated with, located at, or serving as the stronghold or residence for another entity.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c060bfc4819092ac591692a6ccd5 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.