Triple
T12476160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-Masonic Party |
E298180
|
entity |
| Predicate | firstNationalConventionYear |
P105208
|
FINISHED |
| Object | 1831 |
—
|
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: 1831 | Statement: [Anti-Masonic Party, firstNationalConventionYear, 1831]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstNationalConventionYear Context triple: [Anti-Masonic Party, firstNationalConventionYear, 1831]
-
A.
firstCongressDate
Indicates the calendar date on which the first congress or formal assembly associated with an entity took place.
-
B.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
C.
firstRepublicanElectionYear
Indicates the year in which the first election involving the Republican Party occurred for the given entity.
-
D.
congressBeganOn
Indicates the calendar date on which a particular session or term of a congress officially started.
-
E.
firstConstitutedIn
Indicates the time or context in which an entity (such as an organization, body, or structure) was originally formed or formally established.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e5f8d04819086d1ad4d62364005 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:56 p.m.