Triple
T37695253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Motte |
E938910
|
entity |
| Predicate | hasPartOfType |
P45787
|
FINISHED |
| Object | motte-and-bailey castle components |
—
|
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: motte-and-bailey castle components | Statement: [Castle Motte, hasPartOfType, motte-and-bailey castle components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartOfType Context triple: [Castle Motte, hasPartOfType, motte-and-bailey castle components]
-
A.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
B.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
C.
hasParticleType
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
D.
partOfType
chosen
Indicates that one entity represents a component, segment, or subset that belongs to or is included within the type or category represented by another entity.
-
E.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 3, 2026, 4:18 p.m.