Triple
T198639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justin Trudeau |
E4051
|
entity |
| Predicate | advocacyArea |
P1876
|
FINISHED |
| Object | gender equality |
—
|
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: gender equality | Statement: [Justin Trudeau, advocacyArea, gender equality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocacyArea Context triple: [Justin Trudeau, advocacyArea, gender equality]
-
A.
advocates
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
B.
policyFocus
chosen
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
C.
coversPolicyArea
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
D.
relatedLegislation
Indicates that there exists a legislative document that is connected to, affects, or is otherwise relevant to the subject entity.
-
E.
hasPolicyArea
Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.