Triple
T37695255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Motte |
E938910
|
entity |
| Predicate | primaryRoleInCastle |
P204344
|
FINISHED |
| Object | main defensive mound |
—
|
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: main defensive mound | Statement: [Castle Motte, primaryRoleInCastle, main defensive mound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInCastle Context triple: [Castle Motte, primaryRoleInCastle, main defensive mound]
-
A.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
-
B.
roleInLordValentinesCastle
Indicates that an entity has a specific role or function within the context of "Lord Valentine's Castle."
-
C.
positionWithinCastle
Indicates that one entity is located inside the spatial boundaries of a castle.
-
D.
originalCastleOwner
Indicates that a given person or entity is the first or initial owner of a particular castle.
-
E.
primaryRoleInDominion
Indicates that the subject holds the main or most important functional role within the specified dominion, domain, or sphere of authority.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.