Triple
T38688912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royalist siege of 1646 |
E949201
|
entity |
| Predicate | controlBefore |
P21850
|
FINISHED |
| Object | Royalist control of the 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: Royalist control of the stronghold | Statement: [Royalist siege of 1646, controlBefore, Royalist control of the stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlBefore Context triple: [Royalist siege of 1646, controlBefore, Royalist control of the stronghold]
-
A.
controlledBefore
chosen
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
-
B.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
C.
controlsBehaviorOf
Indicates that one entity has the power or mechanism to direct, regulate, or determine the behavior of another entity.
-
D.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
E.
settingBefore
Indicates that one setting or configuration exists or is applied earlier in time or sequence than another setting.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 4:33 p.m.