Triple
T7194992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monmouth Castle |
E168590
|
entity |
| Predicate | garrisonedDuring |
P75677
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Monmouth Castle, garrisonedDuring, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonedDuring Context triple: [Monmouth Castle, garrisonedDuring, medieval period]
-
A.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
-
B.
laterGarrisonedBy
Indicates that a location or structure was subsequently occupied and used as a military garrison by a specified force or group.
-
C.
garrisonServed
Indicates that a military unit or personnel were stationed at and performed service in a particular garrison or fortified location.
-
D.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
E.
garrisonDuringBattle
Indicates that an entity is stationed to defend or hold a location specifically during the time a battle is taking place.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e9050164819081fd6a11d10f9833 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:51 p.m.