Triple
T12227907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas de Soulis |
E291400
|
entity |
| Predicate | borderLord |
P103895
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nicholas de Soulis, borderLord, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLord Context triple: [Nicholas de Soulis, borderLord, yes]
-
A.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
B.
realmRuled
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
-
C.
firstLordProtector
Indicates that the subject is the first individual to hold the position or title of Lord Protector in relation to the object.
-
D.
powerBehindThrone
Indicates a relationship where one entity secretly or informally controls or strongly influences the authority and decisions of another entity that holds the official position of power.
-
E.
boundEmperorBy
Indicates that one entity has constrained, restricted, or subjugated an emperor through some form of binding control or obligation.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d92468052c819090546f36d009a64f |
completed | April 10, 2026, 4:25 p.m. |
Created at: April 8, 2026, 9:51 p.m.