Triple
T21963078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Lucan |
E542384
|
entity |
| Predicate | notableMilitaryRoleOfTitleHolder |
P146716
|
FINISHED |
| Object | British Army 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: British Army general | Statement: [Earl of Lucan, notableMilitaryRoleOfTitleHolder, British Army general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMilitaryRoleOfTitleHolder Context triple: [Earl of Lucan, notableMilitaryRoleOfTitleHolder, British Army general]
-
A.
notableFormerHolderRole
Indicates that an entity previously held a particular notable role or position.
-
B.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
C.
notableTitleHeld
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
-
D.
notableCommanderOf
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
-
E.
notableCommanderUnder
Indicates that one entity served as a notable military commander under the authority or leadership of another entity.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12458e4488190a04f8d3958854b49 |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb9b75308190addc3dba7b5d5ddd |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 8:01 p.m.