Triple
T30670281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Labour MPs |
E780774
|
entity |
| Predicate | parentParty |
P184383
|
FINISHED |
| Object | Labour Party (UK) |
—
|
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: Labour Party (UK) | Statement: [Scottish Labour MPs, parentParty, Labour Party (UK)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentParty Context triple: [Scottish Labour MPs, parentParty, Labour Party (UK)]
-
A.
mainPartyFamily
Indicates that one entity is a primary party in a relationship or event and the other entity is a family member associated with that main party.
-
B.
otherSignificantParty
Indicates that an entity has another important associated party, such as a key counterpart, partner, or involved participant in a relationship or transaction.
-
C.
spouseParty
Indicates that one party is the spouse (legally married partner) of another party.
-
D.
parentTreatyParty
Indicates that one treaty party stands in a parent or overarching relationship to another treaty party within a hierarchical treaty structure.
-
E.
parentService
Indicates that one service functions as the higher-level or owning service in relation to another, which depends on or is derived from it.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 29, 2026, 8:31 p.m.