Triple
T28484874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Parliament 2010–2015 |
E720800
|
entity |
| Predicate | lordsLeader |
P65676
|
FINISHED |
| Object | Lord Strathclyde |
—
|
NE NERFINISHED |
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: Lord Strathclyde | Statement: [UK Parliament 2010–2015, lordsLeader, Lord Strathclyde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lordsLeader Context triple: [UK Parliament 2010–2015, lordsLeader, Lord Strathclyde]
-
A.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
B.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
C.
leaderOfGroup
chosen
Indicates that an entity holds a leadership role or primary authority over a particular group.
-
D.
holyLeagueLeader
Indicates that the subject serves as the leader of a Holy League, an alliance formed for religiously motivated political or military purposes.
-
E.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f0efb7c81909689430f9feec052 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:57 a.m.