Triple
T24085300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Forth |
E596624
|
entity |
| Predicate | holderMilitaryRole |
P9463
|
FINISHED |
| Object | Royalist general |
—
|
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 general | Statement: [Earl of Forth, holderMilitaryRole, Royalist general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderMilitaryRole Context triple: [Earl of Forth, holderMilitaryRole, Royalist general]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
C.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
D.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
E.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc28a7cc81909c76d9d992ac21dc |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.