Triple
T27716375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Party Parliamentary Pro-Life Group |
E698828
|
entity |
| Predicate | crossParty |
P170977
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [All-Party Parliamentary Pro-Life Group, crossParty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossParty Context triple: [All-Party Parliamentary Pro-Life Group, crossParty, true]
-
A.
crossBorderPartner
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
-
B.
crossWith
Indicates that one entity intersects or passes over/through the path, boundary, or position of another entity.
-
C.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
-
D.
crossCut
Indicates that one entity intersects or passes through another, typically cutting across it from one side to the other.
-
E.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 3:04 p.m.