Triple
T31138985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John de Courcy |
E793727
|
entity |
| Predicate | regionConquered |
P164235
|
FINISHED |
| Object | much of Ulster |
—
|
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: much of Ulster | Statement: [John de Courcy, regionConquered, much of Ulster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionConquered Context triple: [John de Courcy, regionConquered, much of Ulster]
-
A.
realmConqueredBy
chosen
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
B.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
C.
gainedTerritory
Indicates that one entity has acquired control over additional land or area from another entity or from a neutral state.
-
D.
lastTerritoriesConqueredBy
Indicates that the referenced territories are the most recent ones taken control of through conquest by a specified entity.
-
E.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 29, 2026, 9:05 p.m.