Triple
T7486116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Federalist No. 31 |
E176885
|
entity |
| Predicate | politicalDomain |
P18467
|
FINISHED |
| Object | American federalism |
—
|
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: American federalism | Statement: [The Federalist No. 31, politicalDomain, American federalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalDomain Context triple: [The Federalist No. 31, politicalDomain, American federalism]
-
A.
politicalSphere
chosen
Indicates involvement or relevance within the domain of politics, governance, or public policy activities and interactions.
-
B.
policyDomain
Indicates the thematic or subject-matter area to which a given policy, rule, or regulatory action belongs.
-
C.
politicalCategory
Indicates the political classification or ideological grouping that an entity belongs to or is associated with.
-
D.
politicalControl
Indicates that one entity holds governing authority, influence, or decision-making power over the political actions or structure of another entity.
-
E.
politicalFunction
Indicates that an entity holds, performs, or is associated with a specific role, duty, or function within a political system or structure.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f556955c8190bf014a065e04c5d8 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.