Triple
T2325189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federalist No. 10 |
E48271
|
entity |
| Predicate | proposesSolutionTo |
P19560
|
FINISHED |
| Object | control of factions |
—
|
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: control of factions | Statement: [Federalist No. 10, proposesSolutionTo, control of factions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesSolutionTo Context triple: [Federalist No. 10, proposesSolutionTo, control of factions]
-
A.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
B.
resolutionIdea
chosen
Indicates a proposed method, plan, or approach intended to resolve or address a particular issue, conflict, or problem.
-
C.
aimsToSolve
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
-
D.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
E.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.