Triple
T6721872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norman keep |
E153415
|
entity |
| Predicate | positionInCastle |
P53325
|
FINISHED |
| Object | central stronghold |
—
|
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: central stronghold | Statement: [Norman keep, positionInCastle, central stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCastle Context triple: [Norman keep, positionInCastle, central stronghold]
-
A.
positionWithinCastle
chosen
Indicates that one entity is located inside the spatial boundaries of a castle.
-
B.
castlePosition
Indicates the spatial location or placement of a castle relative to a reference point or area.
-
C.
castleStatus
Indicates the current condition or state of a castle, such as whether it is intact, damaged, occupied, abandoned, or under construction.
-
D.
positionInCast
Indicates the specific role or placement an individual holds within the cast of a production, such as their billing order or credited position.
-
E.
positionInCasteSystem
Indicates the relative social rank or standing an entity holds within a hierarchical caste system.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d139d50c81908b19120f139deaa5 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.