Triple
T6247002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Aubrey |
E139743
|
entity |
| Predicate | politicalCareer |
P8523
|
FINISHED |
| Object | Member of Parliament |
—
|
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: Member of Parliament | Statement: [Jack Aubrey, politicalCareer, Member of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalCareer Context triple: [Jack Aubrey, politicalCareer, Member of Parliament]
-
A.
politicalFunction
Indicates that an entity holds, performs, or is associated with a specific role, duty, or function within a political system or structure.
-
B.
professionOfCandidate
Indicates that one entity is the profession or occupational role held by the candidate entity.
-
C.
hasPoliticalPositionOn
Indicates that an entity holds or expresses a specific stance, view, or opinion regarding a political issue, policy, or topic.
-
D.
hasPoliticalRole
chosen
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
E.
politicalSupporter
Indicates that one entity supports, endorses, or aligns with the political views, actions, or position of 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631f511c81908d413320efdce42e |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.